delete_repository

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond restating the HTTP verb – no cascade effects, no confirmation requirements, no indication of whether the deletion is immediate or asynchronous, and no auth/permission notes.

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, front-loaded with the action and followed by the endpoint; nothing is padded. The brevity is efficient but tips toward under-specification rather than true conciseness.

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, non-reversible operation with no output schema and zero parameter documentation, the description is far too thin. An agent gets no information about consequences of deletion, error conditions, or how the call reports success.

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 0% and both parameters are undocumented integers with only a minimum constraint. The URL template gives the only semantic hint, mapping project_id and repository_id to path segments, but it adds nothing about format, scope, or what happens when an ID is invalid.

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 ('Removes repository') and even names the exact endpoint, so there is no ambiguity about what the call does. It does not explicitly distinguish itself from siblings like update_repository or get_repository, but the verb makes the distinction self-evident.

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?

There is no guidance on when to use this versus update_repository or list_repositories, no preconditions, and no warning about what deleting a repository implies for attached templates or other dependents. The agent must infer all usage context.

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