edubase_delete_user

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds value beyond that by specifying which users are eligible for deletion and instructing confirmation with the user first. It does not elaborate on irreversible data loss or what happens to related account data, but the destructive hint covers the core risk.

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?

Two short sentences with no filler. The action is front-loaded and both additional sentences carry useful constraints that an agent needs before invoking a destructive operation.

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 one-parameter destructive tool with no output schema, the description gives the action, eligibility restriction, and a safety confirmation instruction. It is slightly thin on what the deletion entails beyond the account record, but the annotations cover destructiveness and the simple schema keeps the context manageable.

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 documentation covers the single parameter (user, 'user identification string') at 100%, so the schema carries the semantic load. The description adds no additional format, source, or resolution details for the user identifier, so baseline 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?

States a specific verb and resource: 'Delete a user account.' This clearly distinguishes it from sibling tools that target related but different resources such as delete_user_login, delete_user_classes, and delete_user_organizations.

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?

Provides explicit eligibility conditions ('Only the users created through the API or generated by the current user can be deleted') and a required confirmation step, which tells the agent when the tool is applicable and when not. No alternative is named, but the exclusion is explicit enough to route correct usage.

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