edubase_delete_integration

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds no extra behavioral context, such as what happens to associated permissions, keys, or tags upon deletion. No mention of side effects.

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?

At only two words, it is too terse. While concise, it sacrifices essential detail for a destructive tool. A slightly longer description would improve clarity.

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 domain (many integration-related tools) and no output schema, the description is severely incomplete. It does not state that deletion is permanent, what the response looks like, or any constraints (e.g., cannot delete if used by something).

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 coverage is 100% (parameter 'integration' described as 'integration identification string'). The description adds no additional meaning beyond that, but baseline is 3 due to full coverage.

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 'Remove integration' clearly states the verb and resource, and the name distinguishes it from sibling delete tools (e.g., edubase_delete_class_members). However, it could be more specific (e.g., 'permanently delete an integration').

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?

No guidance on when to use this tool versus alternatives like edubase_patch_integration or edubase_post_integration. No conditions or pre-requisites are mentioned, despite destructiveHint being true.

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