docs_set_paragraph_style

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions applying styles but does not state whether existing styles are replaced, how the range is interpreted, or any side effects or permissions required for this mutation.

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, using two sentences to state the action and list supported styles. It is efficient with no padding, though additional parameter details would improve it without harming conciseness.

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 no annotations, 0% schema coverage, and a mutation tool with 4 parameters, the description is under-specified. It provides style values but lacks index semantics, behavioral effects, and usage guidance, making it incomplete for safe and correct invocation.

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 must compensate. It lists the style values and mentions 'range,' but does not explain the semantics of document_id, start_index, or end_index (e.g., index type or units). This leaves most parameters underdocumented.

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 action: 'Apply a paragraph-level named style — heading, title, subtitle, or normal text — to a range in a Google Doc.' It uses a specific verb, names the resource, and lists the supported styles, which distinguishes it from sibling tools like docs_format_text or docs_set_alignment.

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 guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. It only implies usage for setting paragraph styles, with no comparison to sibling tools such as docs_format_text.

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