set_page_size

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

No annotations are provided, so the description must carry the full burden. It explains the parameters but does not disclose behavioral traits such as whether the operation modifies the entire document or only sections, idempotency, side effects, or potential errors. More detail is needed for a transparent description.

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 concise, front-loaded with the purpose, and includes the parameter details in a structured manner. Every sentence serves a purpose without 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?

For a simple setter tool with three parameters, the description is complete. It covers the purpose, parameter semantics, and usage context. The presence of an output schema (not shown) reduces the need to describe return values.

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 0%, so the description adds significant meaning beyond the input schema. It provides typical page size examples for width_mm and height_mm and explains the special meaning of para_id (section break vs. body section). This compensates well for the lack of schema descriptions.

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: 'Set page size from millimetre values.' This is specific, with a verb and resource, and distinguishes it from sibling tools like set_page_margins or set_page_orientation.

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 provides context with examples for standard page sizes (A4, Letter) and explains the para_id parameter (None for body section). However, it does not explicitly mention when not to use this tool or list alternatives, which would improve the score.

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