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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveness, so safety is covered. The description adds meaningful context beyond that: the dataset is CC BY 4.0, it is built from the site's calculator test vectors, and it returns a download link and citation guidance. It does not, however, disclose pagination bounds or item counts.

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 main purpose is front-loaded in the first clause, followed by item contents and the paging/citation note. It is dense but every element (units, tolerance, citation, download link) earns its place; the trailing fragment is slightly abrupt but not wasteful.

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?

With an output schema present, return values need not be explained, and the description covers content, paging granularity, unit systems, licensing, and citation. The only minor gap is the absence of guidance on tool choice versus similar read tools, which is not strictly required for correct invocation.

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%, so the schema already fully documents page, detail, and calculator, including defaults and the slug pattern. The description reinforces the page-vs-calculator scoping but adds no format or syntax detail beyond the schema, so 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?

States a specific verb ('Returns items of') and a precisely named resource (the Construction Quantities Benchmark), then enumerates exactly what each item contains (inputs, prompt, expected answer, tolerance, worked steps). This distinguishes it clearly from siblings like get_calculator, get_example, and get_sources.

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?

The description implies the two usage modes ('A page of calculators at a time or one calculator's items'), which maps to the page vs calculator parameters, but it never states when to prefer this tool over related siblings such as get_calculator or get_example, nor any exclusions.

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