site_delete_data

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

Adds beyond annotations: declares irreversibility, force requirement, and server protection for internal keys. Annotations already indicate destructiveness, so description enhances understanding.

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?

Two sentences, highly concise and front-loaded. Every sentence adds essential information without redundancy.

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?

Adequate for a simple delete tool: explains effect, prerequisite (force), and restriction (internal keys). No output schema but completeness is reasonable given low complexity.

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?

Only 33% schema description coverage; description compensates by explaining the 'key' parameter's restriction on internal_* and the 'force' parameter's necessity. The 'site' parameter remains unelaborated.

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?

Clearly states the action 'Delete site.data.<key>' with the HTTP method. It specifies the resource 'site.data.<key>' and distinguishes from sibling tools like page_delete_data by referencing site.data.

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?

Provides conditions: requires force=true and warns against internal_* keys. Does not explicitly compare to alternatives, but the context is sufficient for proper use.

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