batch_format_paragraphs

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

With no annotations provided, the description alone must disclose behavioral traits. It indicates a mutation (applying style) but lacks details on reversibility, side effects (e.g., track changes), required permissions, or behavior with invalid indices. The return value is mentioned, but deeper behavioral context is missing.

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 single-sentence purpose followed by clear Args and Returns sections. Every sentence is informative, no fluff, and the action is front-loaded, making it easy to parse.

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 tool's complexity (batch operation, 3 parameters) and presence of an output schema, the description covers the essentials but lacks completeness. It does not address error scenarios, style existence validation, or behavior with empty ranges, leaving some gaps for a full understanding.

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 explains that style_name is the style name, start_index defaults to 0, end_index is exclusive and defaults to all remaining. This adds value beyond the schema titles but lacks details on valid style names, error handling, or out-of-range behavior.

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 'Apply a style to a range of paragraphs,' specifying the verb (apply) and resource (style to paragraphs). This distinguishes it from sibling tools like add_heading or set_paragraph_text, which focus on different operations.

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 formatting paragraphs by style but does not explicitly state when to use this tool versus alternatives like set_paragraph_text or add_heading. No when-not conditions or alternative tools are mentioned, leaving the agent to infer context.

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