set_page_size

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Set page size' without mentioning that it is a mutation, potential side effects like document reflow, required permissions, or that it modifies the current or specified section. This is insufficient for a write operation.

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 very concise: one sentence for purpose followed by a clear list of arguments. No extraneous information, and the most important detail (the action) is front-loaded.

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 tool with three parameters and an output schema, the description covers the core functionality and parameter semantics. It could be improved by explaining the effect on document sections or that it is a destructive operation, but it is largely sufficient.

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?

Despite schema coverage being 0% (likely a misreport), the description thoroughly explains each parameter: width_mm and height_mm with units and common values, para_id with its purpose and default. This adds significant meaning beyond the schema's titles and types.

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 a specific verb (set) and resource (page size), and it distinguishes from sibling tools like set_page_margins and 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 examples for common page sizes (A4, Letter) and explains the para_id parameter, offering implicit guidance. However, it lacks explicit when-to-use or when-not-to-use instructions and does not mention alternatives among siblings.

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