octo_delete_extensions

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. As a destructive delete operation, it fails to mention permanence, irreversibility, or any consequences (e.g., whether deletion cascades to associated data). The minimal statement provides no behavioral context beyond the action itself.

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, concise sentence with no filler or repetition. It efficiently communicates the core action and target resource.

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 destructive nature and absence of annotations or output schema, the description is incomplete. It does not warn about permanence, explain the team context, or describe expected outcomes. A more complete description would include at least an irreversibility warning and clarify the scope.

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?

The schema covers 100% of the parameter 'uuids' with a description ('List of extension UUIDs to delete'). The tool description adds 'by UUID', which is redundant with the schema. No additional semantic value is provided beyond what the schema already offers.

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 the resource 'team extensions', with the scoping criterion 'by UUID'. It distinguishes itself from siblings like octo_get_extensions (retrieval) and octo_get_tags (tag management) by being explicitly a deletion operation.

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?

No guidance is provided on when to use this tool versus alternatives, or any prerequisites or context. The description simply states the action without specifying scenarios, exclusions, or relationships to other extension-related tools.

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