github_users_delete_attestations_by_subject_digest

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

No annotations provided. The description merely restates the name without disclosing destructive nature, permissions, rate limits, or side effects. It fails to add behavioral context beyond the name.

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?

Single sentence with no wasted words. It is appropriately concise for a straightforward deletion operation, though it could benefit from additional context.

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, no annotations. The description does not explain the scope (user-specific attestations), return value, or confirmation. For a deletion tool, this lacks critical 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?

Schema coverage is 100% with descriptions for both parameters. The description adds 'by subject digest' which is already obvious from the name. Baseline score of 3 is appropriate as the description provides no extra meaning.

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 by subject digest' clearly states the action (delete) and the resource (attestations) with specific criterion (subject digest). It distinguishes from siblings like 'delete_attestations_by_id' and 'delete_attestations_bulk'.

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. Siblings include 'delete_attestations_by_id' and 'delete_attestations_bulk', but the description offers no context for selection.

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