Begin a new annotation cycle

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description adds the behavioral detail that this tool 'unlocks' access after explicit confirmation, which is a useful side effect beyond static annotations. No contradiction detected.

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 two concise sentences with no filler. Front-loaded: the first sentence states the core action, and the second gives usage context. Every word 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?

Given no parameters and no output schema, the description covers the essential purpose and usage. It could mention expected outcomes (e.g., 'returns success') but is largely complete for a simple initialization tool.

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 input schema has no parameters (0 params, 100% coverage). Per calibration guidelines, 0 params baseline is 4. The description does not need to add parameter info, and it correctly omits any.

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 'unlocks annotation access for newly collected Handy transcripts after explicit confirmation', which is a specific verb-resource-action. The title 'Begin a new annotation cycle' reinforces its role as the initial step, distinguishing it from sibling tools like 'save_annotation_and_next' or 'annotation_summary'.

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 advises 'Use from a fresh annotation task', providing clear context for when to invoke it. However, it does not explicitly state when not to use it or mention alternatives, though the sibling tools imply other stages.

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