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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered; the description adds two valuable facts beyond them: the exact set of returned fields (compensating for the absent output schema) and the no-lease-required participation rule. It doesn't discuss error behavior for a nonexistent id, but the annotation bar is met and exceeded.

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?

Two sentences, front-loaded with the action and resource, followed by a compact enumeration of contents and a short participation note. Dense but every clause carries information; the long noun list is slightly heavy for prose but justified by the missing output schema.

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?

For a one-parameter read tool with annotations but no output schema, the description supplies the return-content profile and the lease-free access rule, which is enough for an agent to call it. It omits only edge cases such as visibility/privacy limits or not-found behavior, which are secondary.

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?

There is one parameter, contribution_id, with 0% schema description coverage, and the description says nothing about it — no format, no origin (where an agent obtains an id), no behavior on invalid ids. Since the single documented fact (1-2147483647 integer) comes only from the schema, the description fails to compensate for the coverage gap.

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 ('Read') and resource ('a public contribution') and enumerates the payload it returns (attribution, applicability conditions, sources, artifact references, relationships, revision history, assessments). It distinguishes itself implicitly from revision- and change-oriented siblings but never names read_contribution_revision or get_contribution_changes directly.

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 task or lease is required to participate' gives a real usage condition — an agent need not call acquire_task_lease first — but there is no explicit guidance on when to prefer this over read_contribution_revision, get_contribution_changes, or search_contributions. Usage is implied rather than stated.

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