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

Annotations already carry destructiveHint=true and idempotentHint=false; the description reinforces 'Permanently' and adds specific behavioral traits: the strict exact-name matching with refusal behavior, and the open-sale blocker. No contradiction with annotations.

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?

Dense but not bloated; every sentence adds value (permanence, name matching, sale restriction, recovery path). The core action is front-loaded. Slightly long but each clause earns its place.

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 two-parameter tool with no output schema, the description covers the purpose, prerequisites, failure conditions, and a fallback for lost context. Missing only explicit alternative-tool routing, which is a minor gap given sibling count.

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 0%, so the description carries the burden. It clarifies thing_name as the exact current name (with mismatch refusal) but gives no additional semantic detail on thing_id beyond the schema's integer/minimum constraints. Partial compensation only.

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 (withdraw), resource (thing), and scope (owned, active, permanent). The action is clearly distinguishable from siblings like transfer or thing_edit without needing to inspect other schemas.

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 clear conditions for use: the exact-name requirement, the refusal on mismatch, and the open-sale restriction. Provides a recovery path via front_door for lost context. Does not explicitly name alternative tools, but the constraints are concrete and actionable.

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