set_paragraph_indentation

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

With no annotations, the description carries full burden. It discloses that first_line_cm and hanging_cm are mutually exclusive and that None values leave indent unchanged. However, it omits details like what happens if the paragraph doesn't exist or if the document is not open.

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 with a clear title line followed by a structured list of arguments. Every sentence is necessary and directly useful, with no fluff.

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 5 parameters, no schema descriptions, and existing output schema, the description covers parameter semantics well. However, it lacks context about prerequisites (e.g., document must be open, paragraph must exist) that would aid an agent's decision.

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 coverage is 0%, so the description must add meaning. It clearly explains each parameter's role, units (cm), default behavior (None = unchanged), and mutual exclusivity, adding significant value beyond the schema titles.

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 indentation on a paragraph,' using a specific verb and resource. It distinguishes from sibling tools like set_paragraph_border and set_paragraph_shading by focusing solely on indentation.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for modifying paragraph indentation but lacks when-not or exclusionary advice.

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