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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes beyond them by naming the required connectors:write scope and config:write capability plus the consequence that installs from that host lose their credential. It stops short of stating whether the removal is reversible or recoverable via save_sandbox_registry.

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, no filler, with the mutation and its identifier source front-loaded before the downstream consequence. Every clause carries information an agent needs.

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 one-parameter destructive delete with no output schema, the description covers identity, parameter source, required auth scopes, and the effect on sandbox builds. Nothing material to correct invocation is missing.

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 coverage is 100% and the single parameter's schema description already says 'Registry credential id, from list_sandbox_registries'. The description repeats that provenance without adding format or validation detail, 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) plus resource (stored credential of a private registry) and clarifies the identifier source with '(an id from list_sandbox_registries)'. This distinguishes it cleanly from save_sandbox_registry, list_sandbox_registries, and delete_sandbox_template.

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?

Points the agent at list_sandbox_registries as the way to obtain the required id, and explains the context of use via the downstream effect on sandbox builds. There is no explicit when-not-use or named alternative for removing only part of a credential set, so it falls short of a 5.

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