set_run_strikethrough

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

No annotations are provided, so the description carries the burden. It only describes parameters without mentioning side effects, whether the operation is reversible, or if it replaces existing strikethrough. This is minimal disclosure for a mutation tool.

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 short and to the point, with a clear header and list of parameters. Each sentence is necessary, and the structure is efficient.

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 tool's simplicity and the presence of an output schema (implied by 'Has output schema: true'), the description covers the essential parameters but lacks any mention of the tool's mutating nature or expected return values, which would be helpful for an agent.

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 0% (no schema descriptions). The description adds meaning for the 'double' parameter by explaining its boolean values. However, 'para_id' and 'run_idx' are only restated without additional context beyond the schema property names.

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 'Set strikethrough on a specific run in a paragraph.' It identifies the resource (run) and action (set strikethrough) precisely. However, it does not explicitly differentiate from sibling tools like set_run_underline, though the name and context suffice.

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 lists parameters with brief explanations, including the meaning of the 'double' argument. It does not provide explicit guidance on when to use this tool versus alternatives, but the context of setting strikethrough is implicit.

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