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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered there. The description adds the confirmation gate, but that requirement is also encoded in the required user_confirmed parameter, so the marginal context is thin – no statement on irreversibility or error behavior for a non-matching name.

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?

One sentence, front-loaded with the action, and every clause carries information: what is deleted, how it is identified, and the gating condition.

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 two-parameter destructive tool with annotations covering safety and an output schema covering the return value, the description supplies the action and the confirmation gate, which is enough to call it correctly. Missing only edge-case guidance such as behavior when no exact match exists.

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 description coverage is 100% and both parameters are documented there, including the exact-match semantics of name and the meaning of user_confirmed. The description's 'exact name' phrasing restates the schema rather than extending it, so the baseline 3 applies.

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 (delete) and resource (a saved contact) plus the lookup key (exact name), which cleanly separates it from save_contact, update_contact, and the call_* siblings. An agent can select it without opening the schema.

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 the key precondition – deletion only happens after the user confirms – which is the main thing an agent needs to know before invoking. It stops short of naming alternatives or when-not-to-use cases (e.g., what to do if the name is not an exact match).

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