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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description reinforces it but also adds genuinely non-structured semantic caveats — the format example is 'not an actual finding', AIO's interpretation is 'not expert-reviewed', and there is 'no verdict that the model agrees or disagrees' with the court decision. It does not, however, say what happens on an unknown taskId.

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 purpose and read-only guarantee are front-loaded and each clause carries information (layer definitions, caveats). It is a dense single paragraph heavy on em-dashes and parentheticals, which costs a little readability but wastes no sentences.

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?

There is no output schema, so the description must describe the return shape — and it does, laying out the data-observation, interpretation, court-decision and comparison layers and what each contains. For a read-only single-fetch tool whose annotations carry the safety profile, nothing an agent needs is missing.

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% and the single parameter's description already gives the source list and a concrete example id, so the schema does the heavy lifting. The prose adds no format or validity detail beyond that; baseline 3 applies.

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 names a specific verb and resource ('Fetch one contribution task in full') and enumerates exactly what comes back: question, materials, format example, completion criteria, public scope, plus layered evidence. The word 'one' and 'in full' clearly distinguish it from the sibling list_contribution_tasks, which the parameter description also references.

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?

Usage is only implied: 'Read-only: calling this never submits, registers, or sends anything' steers agents away from using it for submission, and the schema points at list_contribution_tasks for obtaining the id. But there is no explicit when-to-use statement, no statement of prerequisites, and no named alternative for the fetch-one case.

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