github_private_registries_delete_org_private_registry

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

With no annotations provided, the description is the sole source of behavioral information. It implies destructiveness ('Delete') but does not explicitly state that the operation is irreversible, requires specific permissions, or has any side effects. More transparency is needed for a mutation tool.

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 a single sentence of 6 words, extremely concise and front-loaded. However, it could include additional critical details without becoming overly verbose. Still, for a simple delete operation, the structure is acceptable.

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 potentially destructive operation like deleting a private registry, the description lacks crucial context: it does not mention irreversibility, required admin permissions, or any post-deletion consequences. With no output schema, agents have no information about return values. This is incomplete for safe invocation.

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% (both 'org' and 'secret_name' have descriptions), but those descriptions are just the parameter names, offering no additional meaning. The tool description adds nothing beyond the schema, so a baseline score of 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 'Delete a private registry for an organization' clearly states the verb (Delete), resource (private registry), and scope (for an organization), effectively differentiating it from sibling tools like create, get, update, and list.

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 provides no guidance on when to use this tool, prerequisites, or when not to use it. Among a large set of sibling tools (including other private registry operations and many other tool categories), there is no context to help an agent decide between similar operations.

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