Delete Page

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

The description adds the specific note that the action is permanent, which goes beyond the destructiveHint annotation by emphasizing the irreversibility. It doesn't detail other side effects, but for a delete operation, this is sufficient context.

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, consisting of two short sentences with no redundancy or unnecessary detail. It is well-structured and directly conveys the essential 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 simple delete operation, the description fully covers the necessary context: what is being deleted, from where, and that it is permanent. No additional explanation is required, and the output schema is not needed to clarify the action.

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 schema already provides descriptions for both parameters (page_url and course_id), covering 100% of them. The tool description does not add any additional meaning or clarification about these parameters, so the 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 states a clear verb ('delete'), the resource ('wiki page'), and the scope ('from a course'), and explicitly notes that the action is permanent, leaving no ambiguity about what the tool does.

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 does not explicitly mention alternatives like 'edit' or 'create', but the permanence warning implies caution. Given the straightforward nature of a delete operation and the surrounding tool list, the usage context is clear enough.

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