Estimate pages and sheets

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description reinforces this with 'Does not print' plus a useful behavioral nuance: non-PDF files are 'conservatively estimated.' That estimation heuristic is genuine added context not present in the annotations.

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?

Three short sentences, no filler, with the preview/estimate purpose front-loaded before the disclaimer. Slightly terse given the complexity, but nothing is wasted.

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 10 parameters and no output schema, the description should say more about what the estimate returns (per-file counts, totals, sheet math) and how filtering options like recursive/extensions affect scope. It gives only the headline behavior.

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 only 40% across 10 parameters; copies, duplex, max_files, recursive, extensions and pages carry no description in either place. The description mentions no parameter behavior at all, so it fails 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?

States a specific verb and resource: 'Previews selected files and estimates PDF pages and paper sheets before printing.' 'Does not print' crisply separates it from print_paths/quick_print, though it never names a sibling explicitly.

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 phrase 'before printing' implies the workflow position, but there is no explicit when-to-use vs inspect_print_job or when-not guidance, and no mention of alternatives such as print_paths.

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