github_orgs_delete_attestations_bulk

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

With no annotations, the description must disclose behavioral traits. It only states a destructive action without indicating permissions required, irreversibility, effects on related data, or any constraints on the bulk operation. The description is insufficient for safe agent decision-making.

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 short sentence, which is concise but at the expense of necessary detail. It lacks structure (no usage notes, no parameter hints). Adequate length but not optimal for information delivery.

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 complexity of a bulk delete operation with a free-form body parameter and no output schema, the description is severely incomplete. It omits essential details like how to specify attestations, expected behavior, error conditions, and post-deletion verification. The presence of many siblings further necessitates more context.

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?

Although schema description coverage is 100%, the descriptions are minimal: 'org' and 'Request body (JSON object)' with no additional meaning. The description does not clarify what keys the body should contain or how to specify which attestations to delete, failing to add value beyond the schema.

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 attestations in bulk' clearly states the action (delete) and the resource (attestations) with scope 'in bulk', distinguishing it from related tools that delete by ID or subject digest.

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 versus alternatives like github_orgs_delete_attestations_by_id or github_orgs_delete_attestations_by_subject_digest. No usage context or exclusion criteria are mentioned.

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