text_applyParagraphStyle

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

With no annotations provided, the description carries the full behavioral burden but states nothing beyond the mutation itself. It does not say whether applying a style overwrites direct formatting, whether the named style must exist, or what happens when paragraphIndex is omitted.

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?

A single eight-word sentence front-loads the verb and resource with zero filler. It is efficient, but efficiency here mostly reflects how little it says rather than disciplined editing of rich content.

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?

For a 5-parameter mutation tool with no annotations and no output schema, this description is under-specified: parameter targeting, style-name validity, and the optional paragraphIndex are all unexplained. The only documented parameter lives in the schema, not the description, so the definition does not stand on its own.

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 only 20% (just document_id), so four of five parameters are undocumented. The description's 'text range' doesn't explain the pageIndex/frameIndex/paragraphIndex addressing scheme at all, and it never clarifies that paragraphIndex is optional or what its default behavior is.

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 verb+resource (apply a paragraph style) is specific and clearly distinct from the sibling text_applyCharStyle, so an agent knows what operation this is. However, it offers no differentiation from style_listParagraph or style_createParagraph, and the phrase 'text range' is a loose fit for a tool whose parameters actually target a page/frame/paragraph.

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?

There is no when-to-use guidance, no prerequisites (must the style already exist?), and no mention of alternatives such as text_applyCharStyle or style_listParagraph for discovering valid style names. The agent must infer the workflow entirely from the schema.

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