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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds nothing beyond that — no return shape, ordering, pagination, or volume context for a list tool with no output schema.

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?

A single compact sentence fragment with no waste, though it is not front-loaded with a verb phrase and reads more like a label than guidance.

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?

Adequate for a trivial read-only list tool, but with no output schema the description should at least hint at what each returned cost code contains (code, name) and whether the list is complete or paginated.

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 100% and the single optional 'search' param is fully documented as matching code or name, so the baseline of 3 applies. The description contributes no additional meaning about filtering behavior.

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?

Identifies the resource (cost codes) and grounds it in purpose (to put on estimate, change order and invoice items), which partially separates it from the similarly named list_cost_items. The verb is only implicit (from the name/title), and no explicit sibling contrast is given.

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 implied by the mention that these are codes to place on estimate, change order, and invoice items, but there is no explicit when-to-use statement or reference to alternatives such as list_cost_items.

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