set_paragraph_indentation

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 only states the action and lists parameters, but does not disclose whether indentation is overwritten or additive, whether changes are reversible, or what the output/return value indicates. The mutual exclusivity note is more about parameter semantics.

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 concise and front-loaded. It uses a clear docstring format with bullet points, each earning its place. No redundant information.

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 description covers the key indentation parameters and their semantics. However, it does not mention the return value, though an output schema exists. For a tool with multiple interdependent parameters, it provides sufficient context, but could briefly indicate what the tool returns (e.g., success status or modified paragraph).

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 description adds significant meaning beyond the schema: it explains each parameter's unit (centimeters), the effect of None, and the mutual exclusivity between first_line_cm and hanging_cm. Schema coverage is 0%, so the description fully 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 ('paragraph indentation'), and lists the indent types. However, it does not explicitly differentiate from sibling tools like 'set_formatting' or 'get_paragraph_format', which might also involve indentation changes.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, situations where it should not be used, or how it differs from similar tools such as 'set_paragraph_border' or 'update_paragraph'.

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