delete-policy

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

The description only repeats the action 'Delete', which aligns with readOnlyHint=false, but adds no additional behavioral context (e.g., effects, reversibility, side effects). With annotations already indicating a write operation, the description contributes little beyond stating the obvious.

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, which is concise, but it lacks structure and is under-informative. It conveys the core purpose but nothing more.

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 large set of sibling tools and lack of output schema, the description is incomplete. It does not explain the effect of deletion, whether it is irreversible, or any dependencies. For a destructive tool, 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?

Although the schema defines two parameters (vhost, name) with 0% schema description coverage, the description adds no explanation of what these parameters represent or their expected format. For a tool with two simple parameters, some elaboration would be helpful.

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 'Delete a policy for a vhost' clearly states the action (delete) and the resource (policy for a vhost). It distinguishes this tool from siblings like 'delete-operator-policy' or 'delete-parameter'.

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 'delete-operator-policy' or 'delete-parameter'. No context on prerequisites or limitations.

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