docs_set_margins

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully discloses that omitted sides remain unchanged and that units are points. However, it doesn't mention any side effects, permissions, or edge cases like setting a margin to zero.

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 that immediately states the action and unit, then provides critical usage detail. Very efficient with no wasted words.

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 simple operation and presence of an output schema, the description covers the essential behavior: setting page margins with partial update semantics. It lacks explicit mention of prerequisites like document existence, but this is straightforward for a docs tool. Overall, it is sufficient for a tool with 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?

The schema provides zero descriptions for parameters, so the description must compensate. It adds the meaning that all margin parameters are in points and that omission preserves current values. However, it doesn't describe valid ranges or constraints on numeric values, so it only partially compensates.

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 uses a specific verb ('Set') and resource ('page margins'), clearly distinguishing it from sibling formatting tools like docs_set_alignment. It's immediately clear what the tool does.

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 implicit guidance that any side can be omitted to leave it unchanged, but it does not explicitly state when to use this tool instead of alternatives like docs_set_alignment or docs_set_paragraph_style. This missing exclusion leaves some ambiguity, but the tool's unique purpose helps.

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