github_orgs_delete_attestations_by_id

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Delete', implying a destructive, irreversible action, but lacks details on permissions, side effects, or what happens to associated data.

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 extremely short (4 words) and front-loaded, but it sacrifices necessary detail. Every word earns its place, but the overall structure is too sparse to be helpful.

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?

No output schema. The tool deletes organization-level attestations, but the description does not explain what attestations are, the scope (org-level), or the effect. Given the complexity and sibling tools, it is under-specified.

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 covers both parameters with trivial descriptions (just the parameter name). The description adds no meaning beyond the schema; it merely echoes 'by ID' for attestation_id. With 100% schema coverage, baseline is 3, but value added is minimal.

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?

Description clearly states action ('Delete attestations') and key parameter ('by ID'), matching the function name. However, it does not distinguish from sibling tools like 'github_orgs_delete_attestations_bulk' or 'github_orgs_delete_attestations_by_subject_digest', which have overlapping purposes.

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 on when to use this tool versus alternatives. Sibling tools suggest different deletion methods (bulk, by subject digest), but the description provides no context for choosing among them.

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