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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds only content fields and a broad use case; it does not disclose pagination behavior, ordering, global scope of saved items, or what the returned list contains beyond field names.

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 description is a single short sentence with no wasted words, but it is a sentence fragment with no leading verb and does not front-load the action or key usage context.

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 list tool with four parameters, no output schema, and pagination via limit/cursor, the description is incomplete. It describes the data fields but not the return structure, pagination behavior, filtering semantics, or how the saved items relate to estimates and change orders.

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 50%, with only cursor and search documented in the schema. The description mentions no parameters at all, leaving type and limit semantics unexplained and failing 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?

The description identifies the resource as saved cost items with unit, unit cost, and markup, and hints at their use for pricing estimate and change order lines. However, it never states the action (listing/returning) and does not distinguish this tool from siblings such as list_cost_codes or add_estimate_items.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'to price estimate and change order lines' suggests a use case but does not explain when to call this list endpoint, how to filter, or when not to use it.

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