word_set_paragraph_formats

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

With no annotations, the description must disclose behavioral traits. It only states the operation itself and the target (by paraId) but does not mention whether existing formatting is replaced, what happens if a paraId is not found, any error conditions, or whether it is a mutation with side effects. This is a significant transparency gap.

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, front-loaded sentence that efficiently captures the tool's purpose without wasted words. It is appropriately sized for the operation.

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 is a batch mutation with no output schema and no annotations, yet the description provides no information about return values, error handling, or prerequisites. While the schema covers parameters adequately, the description alone does not give enough context for an agent to understand the full scope of the operation.

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 100%, so the schema documents all parameters (file_path, edits with para_id and optional formatting fields). The description adds no additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 the tool applies paragraph-level formatting (alignment, spacing, indent) targeting paragraphs by paraId. This specific verb+resource+scope distinguishes it from sibling tools like word_format_text (character formatting) and word_edit_paragraphs (content editing).

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 when paragraph formatting such as alignment, spacing, or indent needs to be applied, but it does not provide explicit guidance on when to prefer this tool over alternatives like word_set_headings or word_edit_paragraphs, nor does it mention exclusions or prerequisites.

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