set_line_spacing

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

With no annotations, the description carries the full burden. It explains parameter behavior well (e.g., meaning of None, units for line_value). However, it does not disclose return value, error conditions, or required document state, leaving gaps in overall behavioral understanding.

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 highly concise: a one-line summary followed by a structured Args section. Every sentence adds value, and the format is easy to parse. No redundancy or 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 the presence of an output schema (context says 'Has output schema: true'), the description need not explain return values. It adequately covers parameter semantics and usage. However, it omits prerequisites (e.g., document must be open, para_id must exist) and error handling, which slightly limits completeness.

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%, so the description compensates fully. It adds meaningful semantics for all 5 parameters, including value ranges, units (twips, points), examples (240=double), and behavior of None. This is exemplary 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 it sets line spacing and paragraph spacing, using a specific verb and resource. However, it does not differentiate from the sibling tool 'set_paragraph_format', which could also set paragraph spacing, so clarity is high but not fully distinguishing.

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 modifying line and paragraph spacing, but provides no explicit guidance on when to use this tool over alternatives like 'set_paragraph_format'. The context is implied but lacks exclusions or selection criteria.

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