delete_page

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

The description adds 'This action is permanent,' which aligns with the 'destructiveHint' annotation. However, it does not disclose additional behavioral traits like required permissions or side effects beyond what annotations already convey.

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 with two short sentences. It front-loads the purpose and adds a critical detail about permanence without any redundant words.

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 simple destructive tool with only two required parameters and no output schema, the description is fairly complete. It covers the action and permanence, though it could mention prerequisites or reversibility more explicitly.

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?

The input schema already fully describes both parameters ('course_id' and 'page_url') with clear descriptions. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the action ('Delete a wiki page') and the context ('from a course'), using a specific verb and resource. It distinguishes itself from sibling tools like 'delete_assignment' or 'delete_discussion'.

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 implies usage when needing to delete a wiki page, but it does not provide explicit guidance on when not to use it or alternatives. Given the many delete siblings, more clarity would help, but the purpose is clear enough.

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