apply_style

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Apply' with no mention of side effects, reversibility, permissions, or return behavior. It fails to explain what happens to existing styles or whether the operation is a mutation beyond the implicit meaning.

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?

Two sentences: the first states the action, the second gives selection guidance. The text is front-loaded and every word earns its place, with no unrelated or redundant 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?

The tool has 4 parameters, a complex target union, no output schema, and no annotations, making this description inadequate. It omits crucial context about parameter formats, return values, and operational behavior, leaving an agent without enough information to invoke the tool correctly.

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 only 25% (styleKind has a default), and the description adds no details about the 'style' value (must be an existing style name), the 'target' variants (string, uuid, role, or selection), or 'timeoutSec'. It merely echoes the styleKind enum without clarifying semantics.

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 paragraph, character, or object style to target item(s)' with a specific verb and resource, distinguishing it from style creation/update/list tools. It also mentions the applicable style kinds, aligning with the styleKind enum.

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 explicitly advises 'Prefer execute_batch when combining with other ops,' giving a clear alternative for batch scenarios. This provides conditional guidance for when to use this tool versus a sibling, which is exactly what the dimension looks for.

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