set_run_subscript

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

With no annotations, the description carries the full burden of disclosing behavior. It only states what the tool does, but not side effects (e.g., overwriting existing subscript), constraints (e.g., run must exist), or permission requirements. This is insufficient for safe invocation.

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: one sentence for purpose followed by bullet-style parameter explanations. No superfluous words, and the key information is front-loaded. Every sentence adds value.

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 simple formatting tool with an output schema, the description is partially complete. It lacks usage guidelines and behavioral transparency, which are important for an AI agent to correctly select this among many sibling formatting tools. However, the parameter details are good.

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 description explains both parameters: 'para_id: paraId of the target paragraph' and 'run_idx: Zero-based index of the run.' Given the schema has 0% description coverage, this adds crucial meaning beyond the schema's type and title, though it could include details like bounds validation.

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 tool's purpose: 'Set subscript vertical alignment on a specific run in a paragraph.' It specifies the verb (Set) and resource (subscript vertical alignment on a run), distinguishing it from sibling tools like set_run_superscript or set_run_strikethrough.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., set_run_superscript for superscript). The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage without explicit direction.

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