delete-permission

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

While annotations indicate readOnlyHint=false, implying mutation, the description adds no additional behavioral detail. It does not disclose whether the deletion is irreversible, what permissions are affected (all or specific), or any side effects on connected services.

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 concise sentence with no redundant information. However, it could be more structured by including parameter details or usage hints without sacrificing conciseness.

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's simplicity (two string parameters, no output schema), the description captures the essential action. However, it lacks context about the permission model (e.g., that permissions are vhost-specific) and does not mention related options like delete-topic-permission for topic permissions.

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?

With 0% schema description coverage, the description bears full burden for clarifying parameters. It merely repeats the parameter names ('vhost', 'user') without explaining their meaning, format, or how to obtain valid values. This provides minimal value beyond the parameter names.

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'), the resource ('permissions'), and the scope ('for a user in a vhost'). It effectively distinguishes from sibling tools like set-permission (create/update) and get-permission (read).

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 versus alternatives (e.g., set-permission, delete-topic-permission), nor does it mention prerequisites or consequences of deletion. This leaves the agent without context for choosing the correct tool.

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