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

Annotations already declare destructiveHint=true, but the description goes well beyond them: it names the side effect (the post disappears from list_inspiration), discloses that the removal is recoverable via the website, states the return value (the removed saved_key), and confirms no credits are consumed. Reversibility is exactly the context an agent needs before invoking a destructive tool, and none of it is derivable from the annotation flags.

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?

Four short sentences, front-loaded with the effect, then side effect, then the alternative routing, then the return value and cost. Every sentence carries distinct information; nothing restates the tool name or the schema.

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 one-parameter destructive tool with no output schema, the description covers effect, reversibility, cost, return value, and the alternative tool for the adjacent intent. There is no gap an agent would need to guess at in order to invoke this correctly.

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?

Schema coverage is 100% and saved_key already carries a concrete example (instagram:C8xYz12AbCd), so the schema does the heavy lifting. The description adds the complementary detail that the returned value is that saved_key, closing the loop between input and output for an agent chaining calls.

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?

States a specific verb and resource — removes a post from the creator's saved inspiration list — and immediately names the affected surface (list_inspiration), which is itself a sibling tool. An agent can distinguish this from save_inspiration and delete_library_item without opening any schema.

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?

Gives explicit when-to-use ("clear out posts") and names the alternative plus the exact parameterization for a near-miss case: "to keep a post but move it out of the way, save_inspiration with status archived." That is a rare, concrete disambiguation between two sibling tools.

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