set_page_margins

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

No annotations exist, so the description carries the full burden. It explains that None values leave margins unchanged and para_id targets a specific section. However, it omits details on whether margins apply to the whole document or just the section, and does not mention side effects, authorization needs, or return values.

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 a concise docstring with a clear purpose statement followed by a parameter list. Every sentence earns its place; no fluff or redundancy. Front-loaded with the main action.

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 tool's 5 optional parameters and the presence of an output schema (context signal), the description covers all parameters and their null handling. However, it could be more explicit about whether margins apply to the whole document or a specific section.

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?

With 0% schema description coverage, the description compensates by listing all 5 parameters with clear one-line explanations (e.g., 'Top margin in mm. None = unchanged.'). This adds meaning beyond the schema, although constraints like value ranges or behavior for negative values are missing.

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 'Set page margins from millimetre values', identifying the verb (set), resource (page margins), and unit (mm). It distinguishes from sibling tools like set_page_size or set_section_properties, but does not explicitly exclude other margin-related tools.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or compare to other margin-setting methods.

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