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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: the listing includes completed-but-unopened reviews, which tells the agent results are not limited to pending work. It says nothing about ordering, pagination, or how many results come back.

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?

One short sentence with no padding, and the most distinctive detail (including unopened completed reviews) is placed up front. Nothing is wasted, though there is also very little to structure.

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-only list tool with no output schema and strong annotations, the description is thin but not fatal. The remaining gap an agent actually needs filled is what the required 'id' scopes and whether results are bounded, neither of which is addressed.

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 nominally 100%, but the sole parameter's description is just 'ID', which resolves nothing. The description does not clarify whether that id is the contract ID, a reconciliation ID, or something else, so it fails to compensate for a technically covered but semantically empty schema field.

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 gives a verb (list) and a resource ('contract re-reads'), but renames the resource relative to the tool name 'reconciliations' without explaining the relationship, so an agent has to infer that a 'reconciliation' is a contract re-read. It also never states that listing is scoped to a specific contract, which is the key ambiguity given the single 'id' parameter.

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 versus the closely named sibling clm_get_contract_reconciliation, nor versus clm_list_contracts or clm_get_contract_type_reread. The only implicit hint is the phrase 'completed but unopened reviews,' which suggests a review-queue use case but is not stated as a when-to-use condition.

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