furl_purge

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses permanence ('no undo'), the escape hatch context, offloaded content TTL behavior, and return value. No annotations provided, so description carries full burden and delivers well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no wasted words. First sentence states purpose and context, second explains parameters, third covers return and edge behavior. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with 2 parameters and no output schema, the description covers all essential aspects: action, parameters, return count, and edge cases. Minor omission: behavior if both parameters provided, but mutual exclusivity is implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds value beyond schema: specifies hash format ('12 or 24 lowercase-hex chars'), mutual exclusivity, and non-error on missing hash. Schema already covers descriptions, so credit for extra detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('Permanently erase stored originals from the CCR store'), uses specific verbs ('erase', 'purge'), and distinguishes it from sibling tools (e.g., furl_list, furl_retrieve). The 'escape hatch' metaphor further clarifies its role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Pass EXACTLY ONE of: hash or all=true' and notes that a missing hash is not an error. Does not explicitly contrast with alternatives like furl_compress, but the parameter constraints are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.