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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The field list hints at what comes back, but there is no mention of pagination behavior (limit default 25, cursor continuation) or result ordering, which is the main behavioral detail this read-only list tool actually needs.

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?

It is a single short fragment with no filler, but the terseness comes at the cost of specification rather than being economically front-loaded. There is no leading verb or scope statement to anchor the sentence.

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 filterable, paginated list tool with no output schema, the description should cover paging and filtering; instead it only enumerates fields. The 75% schema coverage and existing annotations partially compensate, but an agent still cannot tell how to page through results or how the filters narrow the list.

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 75% and the bare `limit` property (default 25, max 100) is undocumented in both schema and description. The description mentions none of the four parameters, adding zero meaning beyond the schema for search, project_id, cursor or limit.

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 is a noun phrase listing returned fields ("Sub-contracts with subcontractor, project, amount, billed, paid, balance and status") rather than a verb+resource statement. Combined with the title 'List sub-contracts' an agent can infer it enumerates sub-contracts, but nothing distinguishes it from sibling get_sub_contract, and the tool's own verb never appears in the description.

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?

There is no when-to-use guidance, no mention of the paging model, and no routing to alternatives. An agent gets no signal about when to reach for this rather than get_sub_contract or the many other list_* siblings.

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