Save annotation and load next

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

Description adds sequential behavior (save then return next) beyond the annotations (readOnlyHint=false, destructiveHint=false). However, it does not disclose potential side effects, error conditions, or what happens if no next record exists.

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?

One sentence that is front-loaded and conveys the core action efficiently. No wasted words, but could be expanded to include key details without losing conciseness.

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 tool with five parameters, 20% of which are enums, and no output schema, the description is insufficient. It omits parameter explanations, error handling, and return value details, making it inadequate for reliable invocation.

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 provides no explanation of the five parameters (batchId, recordId, correctedText, status, notes) despite 0% schema description coverage. It does not clarify the meaning of the enum values or required fields.

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 a two-step action: save a user-reviewed transcript target and return the next record. This combines save and navigation, distinguishing it from siblings like 'save_correction_proposals' or 'load_annotation_record'.

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 implies usage in a batch annotation workflow by mentioning 'widget batch' and returning the next record, but it does not explicitly state when to use this tool versus alternatives or when not to use it.

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