set_drop_cap

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

With no annotations, the description carries the full behavioral burden. It only says 'Set' and lists parameters; it does not disclose whether it replaces an existing drop cap, whether style=0 removes it, whether it applies to current selection/cursor, or what side effects occur.

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 compact and well-structured: a one-line purpose followed by an Args block. Every line adds distinct semantic value, with no filler or repetition of the tool name.

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?

All parameters are documented and an output schema exists, so return details are not needed. However, no argument identifies which paragraph is affected, leaving the essential operational detail implicit—likely the current cursor/selection—which is critical for a mutation tool.

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%, but the description compensates fully: it explains doc_id provenance, gives explicit style values (0=none, 1=embedded, 2=marginal), specifies hwpunits for spacing, and defines face_color as an HWP color value.

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 ('Set'), the resource ('drop cap'), and the scope ('for paragraph'), with a helpful parenthetical definition ('initial letter decoration'). No sibling tool targets drop caps, so it is easily distinguished.

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 related paragraph/style tools, nor any exclusions or preconditions such as requiring a current cursor position or selection. The agent must infer usage context entirely from the parameter list.

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