set_character_position

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

No annotations provided, so description carries full burden. It explains the position_pt parameter but does not disclose side effects (e.g., overwriting existing formatting), prerequisites (e.g., run must exist), error handling, or interaction with subscript/superscript formatting.

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?

Short and front-loaded, no fluff. The Args section is slightly redundant given the schema, but it does not harm. Could be trimmed further but is acceptable.

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 (3 params, all required, with output schema), the description covers the effect and parameter semantics well. Lacks details on return value and error conditions, but output schema exists so return format is assumed documented elsewhere.

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?

Description adds meaning for all 3 parameters beyond the schema (which has no descriptions). It explains para_id, run_idx (zero-based), and position_pt (offset meaning). Since schema description coverage is 0%, the description fully compensates.

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?

Description clearly states it sets vertical character position (raised/lowered) for a specific run, using verb 'set' and specific resource. Distinguishes from sibling tools like set_run_subscript or set_run_superscript by focusing on vertical offset.

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 explicit when-to-use or when-not-to-use guidance, nor mention of alternatives. Usage is implied by the description, but without exclusions or comparison to related tools.

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