Get Page Metadata

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

The description discloses that the tool may pre-render the file, which is a behavioral trait. However, with no annotations provided, it does not fully disclose potential side effects (e.g., temporary file creation, performance impact) or permissions required. It is moderately transparent.

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 extremely concise at two sentences, front-loading the core purpose and adding one additional behavioral detail. Every sentence is essential and there is no redundancy.

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?

Given the complexity of the nested parameters and no output schema, the description covers the return values (page count, physical sheets) but does not specify the structure of the response (e.g., per file or aggregate). It is adequate but not fully complete.

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?

The input schema has 100% coverage with descriptions for all parameters. The tool description does not add additional meaning beyond the schema; it only rephrases the return values. Baseline score of 3 is appropriate.

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 clearly states the tool's purpose: retrieving page count and physical sheet information for a file before printing. It uses specific verbs ('get', 'returns') and identifies the resource ('page metadata'). This distinguishes it from sibling tools like print_file or get_default_printer.

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 usage context ('before printing') but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or conditions. There is no guidance on when not to use it or mention of sibling tools.

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