page_delete_data

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

Annotations mark destructiveHint:true, which the description reinforces with 'IRREVERSIBLE' and 'removed permanently'. It also adds context about the force flag and internal key behavior, going beyond annotations. No contradiction.

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 clear sentences: action+HTTP verb, irreversibility, force and internal key rules. No redundant words, front-loaded with key information.

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 single-key delete operation with destructiveHint, the description covers irreversibility, force requirement, and internal key protection. Lacks error conditions or return value, but given no output schema and annotations, it is adequately complete.

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 description coverage is only 25% (force param only), but the description adds meaningful context: it clarifies that force must be true to execute, and explains that keys starting with 'internal_' are rejected. This compensates for low schema coverage for key and force parameters.

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?

Description clearly states 'Delete a single page.data.<key>' with HTTP method, specifying the exact resource and action. It distinguishes from sibling tools like article_delete_data and site_delete_data by focusing on page data under a specific key.

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?

Description explains the critical force=true requirement and internal key protection, but does not explicitly compare to alternatives like article_delete_data or page_delete. It gives functional constraints but lacks when-to-use guidance beyond the tool's own requirements.

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