Delete registry credential

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

Annotations already indicate destructiveHint=true, so the destructive nature is clear. The description adds the HTTP method and endpoint (DELETE /registrycredentials/{registryCredentialId}), providing API-specific context. No additional behavioral traits (e.g., permanence, auth needs) are disclosed, but it is consistent with annotations.

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 two sentences, clear and direct. The first sentence states the purpose, and the second repeats with the API call. Minor redundancy but overall efficient and front-loaded.

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 (1 parameter, no output schema, destructiveHint annotation), the description sufficiently covers the action and endpoint. It lacks prerequisites or side effects, but the annotations fill some gaps. Adequate for expected complexity.

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% with one parameter (registryCredentialId) described as 'The ID of the registry credential.' The description adds 'with the provided ID' but does not enhance meaning beyond the schema. Baseline 3 is appropriate.

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 verb 'Delete' and resource 'registry credential', matching the tool name. It differentiates from sibling tools like render_create_registry_credential, render_update_registry_credential, and render_retrieve_registry_credential by specifying the deletion action.

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 does not explicitly provide guidance on when to use this tool versus alternatives. It only describes the deletion action without mentioning exclusions or related operations like update or create. Use context is implied by the name and purpose.

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