create_paragraph_style

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

With no annotations, the description must carry behavioral information, but it only says 'Create a paragraph style'. Important details are missing: the style is added to the current document, it may overwrite an existing style with the same name, and it does not affect any text until applied. No mention of side effects or required permissions.

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 extremely concise at only 4 words, but it is under-specified to the point of being minimally informative. While it avoids redundancy, it does not earn its place by providing helpful context.

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 parameter count of 8 and no output schema, the description should explain what the tool does in the broader document context. It omits critical details: the style is created in the active document, the name must be unique, and the tool does not apply the style to any text. The description fails to make the tool self-contained.

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?

The input schema provides descriptions for 7 of 8 parameters (88% coverage), so the description adds no extra meaning. The tool name implies the purpose, but the description does not clarify the role of parameters like fontFamily, leading, etc., beyond what the schema already states.

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 verb 'Create' and the resource 'paragraph style', distinguishing it from siblings like create_character_style. However, it lacks any additional context that would help an agent understand what a paragraph style is or how it fits into the document workflow.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as requiring an open document, or that the style name should be unique. No comparison to create_character_style or apply_paragraph_style is provided.

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