github_repos_create_attestation

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

Description only states 'Create' implying mutation, but no details on side effects, authentication needs, rate limits, or what gets created. With no annotations, more disclosure is needed.

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?

Overly terse single sentence. While concise, it lacks necessary detail and does not earn its place as it fails to provide useful information beyond the name.

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 no output schema or annotations, the description should be more comprehensive. It omits what an attestation is, required body structure, and expected outcome.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's brief 'owner', 'repo', and 'Request body (JSON object)'.

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 'Create an attestation' is vague. It does not specify what type of attestation (e.g., artifact attestation, commit attestation) or clarify the context beyond the tool name. Among siblings like list_attestations and delete_attestations, the purpose is not differentiated.

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 vs alternatives (e.g., other attestation tools or creation methods). No context or exclusions provided.

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