edubase_delete_user_assume

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description merely restates the action (revoke) without adding further behavioral context such as side effects, permission requirements, or irreversible consequences, thus adding no value beyond the annotations.

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 a single sentence with no unnecessary words. It is front-loaded with the core action, making it easy for an agent to quickly understand the tool's purpose.

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 tool has one parameter, no output schema, and annotations covering destructive/idempotent behavior, the description adequately states the action. However, it could mention the consequence of revoking the token (e.g., the user loses assumed roles), but the brevity is acceptable for a simple revocation operation.

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 covers 100% of parameters with a description for 'token' as 'assume token'. The description does not add any additional semantic meaning, format, or examples beyond the schema, so it meets the baseline for high schema 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 'Revoke assume token' uses a specific verb 'revoke' and clearly identifies the resource 'assume token'. It is succinct and distinguishes this tool from other delete tools (e.g., edubase_delete_user) by focusing on the assume token entity.

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 provides no guidance on when to use this tool or its alternatives. It does not mention that this tool should be used to revoke an assume token created via edubase_post_user_assume, nor does it explain prerequisites or post-conditions.

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