set_page_margins

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

No annotations are provided, so the description carries the full burden. It indicates a new file is created, but does not explain the behavior of default values (-1), what happens if parameters are omitted, or any side effects. Missing crucial behavioral traits beyond the basic 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 a single sentence, efficiently stating the action and scope. However, the term 'delegate' may be unclear, and a slightly more structured presentation could improve readability.

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 9 parameters, no annotations, and an output schema present, the description is incomplete. It does not explain default behavior, return values, error conditions, or unit details. More context is needed for a tool of this complexity.

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 0%, requiring the description to compensate. It lists the margin parameters and mentions HWPUNIT but does not explain the meaning of -1 defaults, the unit HWPUNIT, or the roles of path and out_path. Adds little value beyond the parameter names.

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 verb 'Set' and resource 'page margins', lists specific margins (left, right, top, bottom, header, footer, gutter), and distinguishes it from siblings by noting it applies to a NEW file (delegate), which differentiates it from tools that modify existing documents.

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 for creating a new file with margins set, but does not explicitly state when not to use it or provide alternatives. Sibling tools like apply_to_open_hwp suggest other use cases, but no guidance is given.

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