delete_discussion

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

Annotations already provide 'destructiveHint: true', but the description adds 'This action is permanent.', which clarifies the irreversible nature. However, it does not disclose potential side effects like cascading deletion of replies or authorization requirements.

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 very concise with only two sentences, front-loading the main action and then adding the key detail of permanence. No unnecessary 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 delete tool with two parameters and no output schema, the description is adequately complete. It covers the essential action and permanence. Could be enhanced by mentioning cascading effects or post-deletion behavior, but not critical.

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?

Input schema has 100% coverage for both parameters ('course_id' and 'topic_id') with clear descriptions. The tool description does not add extra semantics beyond what the schema provides, 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') and the resource ('discussion topic from a course'), with the added note of permanence, distinguishing it from sibling tools like 'delete_assignment' or 'delete_file'.

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 the use case (deleting discussion topics) but does not provide explicit guidance on when to use this tool vs. alternatives like 'update_discussion' or 'create_discussion'. No exclusions or preconditions are mentioned.

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