edubase_delete_integration

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

Annotations already indicate destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no extra behavioral context, such as whether deletion cascades to related resources or whether it is reversible.

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 short (2 words) and front-loads the purpose. It is efficient but somewhat under-specified; however, for a simple tool, it is appropriately concise.

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?

The description is too minimal for a deletion tool. It does not state that deletion is permanent, how to obtain the integration identifier, or what happens to associated data (e.g., permissions, tags). Given no output schema and many sibling tools, more context is needed.

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 covers 100% of the single required parameter 'integration' with description 'integration identification string'. The description adds no additional meaning beyond the schema, which is adequate for a simple string parameter.

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 identifies the verb (remove) and resource (integration), and among siblings like edubase_delete_integration_permission, it is distinct. However, it could be more descriptive (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 (e.g., delete_integration_permission, patch_integration). The description lacks prerequisites, consequences, or context for choosing deletion.

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