set_section_properties

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 clearly states this tool modifies properties, implying a write operation. However, it does not disclose whether changes are reversible, if special permissions are required, or any side effects on the document. While functional, it lacks deeper behavioral context.

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 well-structured: a brief one-line summary followed by bullet-like parameter explanations. It is front-loaded with the main purpose. However, it could be slightly more concise without losing clarity. Every sentence serves a purpose.

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?

The tool has 8 parameters, all optional, and an output schema is present (though not shown). The description explains all parameters thoroughly. It does not explain the return value, but that is acceptable given the output schema. Overall, it provides sufficient context for an agent to use the tool correctly.

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%, meaning the schema provides no parameter descriptions. The description compensates fully by explaining each parameter in detail, including units (DXA, twips), example values (12240 = 8.5 inches), and default behavior (0 = unchanged, empty = body section). This adds significant value beyond the schema.

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 'Modify section properties (page size, orientation, margins).' It specifies the verb 'Modify' and resource 'section properties', and lists the specific properties affected. This distinguishes it from sibling tools like 'add_section_break' which adds a new break, and 'set_properties' which sets global document properties.

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 a clear purpose and specifies that para_id refers to 'paragraph with section break' and that empty means 'body section'. It does not explicitly mention when to use this tool versus alternatives, but the context of modifying existing section properties is implied. Alternatives like adding a section break are distinct operations.

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