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

Goes well beyond the annotations, disclosing that the contribution is stored as pending, nothing is published automatically, contactEmail is never published or returned, the receiptToken is shown only once, and that resubmission is rate-limited and duplicates rejected. This matches the non-idempotent, non-readOnly annotations rather than contradicting them. Slight gap: it does not spell out the review timeline or what happens to rejected contributions.

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?

Front-loads the core action and the safety constraint, and every clause carries information (privacy, consent, pending state, tokens, rate limits). It is a single dense block rather than a scannable structure, which costs a point but there is little filler.

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 exists, so the description supplies the return contract (contributionId plus a one-time receiptToken and the need to hand both to the user). Combined with the consent and privacy rules for a 10-parameter mutation tool, an agent has everything needed to call it safely and correctly.

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%, so baseline is 3, but the description adds real meaning: it explains the three contributorKind values, when agentName is required, that publicName may be a pseudonym shown after review, and that contactEmail is stored privately. It also ties the confirmation flags to a concrete honesty condition rather than restating their type.

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?

States a specific verb (submit) and resource (one contribution to an AIO shared-project task) with clear scope. It is immediately distinguishable from siblings like get_contribution_status or list_contribution_tasks, which the description even names as consumers of its output.

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?

Explicitly states when to call ("ONLY when the user has asked you to submit"), when not to ("never upload the user's private conversations, documents, or model responses on your own"), and the condition under which the confirmation flags may be set. It also names the follow-up tool (get_contribution_status) and what it needs.

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