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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety profile is covered. The description goes beyond that by disclosing what actually gets destroyed (Vault secret material plus the metadata row) and the downstream operational consequence (running deployments may break). It does not cover auth/prerequisite requirements or recoverability, which keeps it from a 5.

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 sentences: the first front-loads what the tool does and its two side effects, the second carries the risk and the recommended alternative. No filler or repetition of the tool name.

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 destructive mutation with no output schema and thin annotations, the description discloses effects, consequences, and an alternative path, which is enough to call it safely. The main remaining gap is the meaning of the `id` parameter, which nothing else in the structured data supplies.

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?

There is a single required parameter `id` with 0% schema description coverage, and the description never mentions it. An agent must infer whether it is the credential ID (from list_broker_credentials) or something else; with no schema text, the description should have compensated and does not.

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 (deletes broker credential material) plus the exact two effects: removal from Vault and marking the user's metadata row deleted. This is clearly distinguishable from create_broker_credential, update_broker_credential, and list_broker_credentials among the siblings.

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?

Gives explicit steering away from rash use: it warns that running deployments may fail and recommends creating a new credential and redeploying instead of deleting an active dependency. It stops short of saying when deletion IS the right choice, but the alternative path is named clearly.

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