delete_page

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

With no annotations provided, the description carries the full burden. It discloses that deletion cannot be undone, which is key behavioral info. However, it omits details like required permissions, cascading effects, or error conditions, leaving gaps in transparency.

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?

The description is extremely concise, using two short sentences with no redundancy. The critical information (action and irreversibility) is front-loaded, making it efficient for an agent to parse.

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?

Given the tool is a simple delete operation with one parameter and an output schema exists, the description covers the essential purpose. However, it lacks context about permissions, error handling, or what happens to related content, which is moderate completeness for a mutation tool.

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 0%, meaning the properties (page_id) have no descriptions in the schema. The description adds only 'by id', which vaguely hints at the parameter's role but does not explain format, examples, or constraints. With one parameter, a more informative description is expected.

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 explicitly states the verb 'delete' and the resource 'page by id', making the tool's purpose unmistakable. It clearly distinguishes from sibling delete tools (e.g., delete_label, delete_post) which target different resources.

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?

The description mentions irreversibility but provides no explicit guidance on when to use this tool versus alternatives or any prerequisites. Usage is implied by the resource name but lacks context like when not to use it.

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