insert_caption

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

With no annotations, the description carries the full burden. It does not disclose side effects (e.g., updating caption numbering), required permissions, or return value. The output schema exists but is not referenced, leaving behavior unclear.

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 concise, using a single sentence and a bullet-like list for arguments. It is front-loaded and wastes no words, though the argument list could be integrated into a more natural prose structure.

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 moderate complexity and no annotations, the description covers the basic purpose and parameters but lacks return information, error handling, or integration context (e.g., how captions interact with lists of figures/tables). An output schema exists but is not described.

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?

Despite 0% schema description coverage, the description provides meaningful explanations for each parameter: 'after_para_id' is defined as the paraId of the paragraph to insert after, 'text' is the description without label/number, and 'label' is the label type with a default. This adds value beyond the schema's type-only definitions.

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 inserts a caption paragraph after a specified paragraph, with a specific verb and resource. It is distinct from sibling tools like insert_text or insert_paragraph, but the description itself does not explicitly differentiate them, relying on the tool name and context.

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, such as insert_text or add_cross_reference. There are no when-not-to-use instructions or mentions of prerequisites like whether the after_para_id must exist.

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