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

The description states the tool records a turn, which is clearly a write/mutation operation, yet the annotations declare readOnlyHint=true. This is a direct contradiction and is deeply misleading for an agent. No other behavioral context is provided.

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 a single, efficiently written sentence that front-loads the core action before mentioning the purpose. It earns a high score, though it sacrifices useful behavioral detail for brevity.

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 7 parameters selection and multiple sibling tools, this description is thin. It does not address the contradiction between the read-only annotation and the write behavior, nor give guidance on selecting among related memory/session tools. The presence of an output schema reduces the need to describe return values, but the other gaps remain.

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 100% parameter description coverage, so the baseline is 3. The description only echoes a few enum values from turn_type (decision, breakthrough, summary) and adds no deeper meaning about parameters like supersedes, track, or session_id.

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 uses a specific verb and resource ('Record a session turn') and adds examples of turn types, which makes the core action clear. It does not explicitly distinguish itself from siblings like memory.create or session.continuity, so it misses the top score.

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 phrase 'so the next session can resume' implies the intended use case: persisting progress for future sessions. However, there is no explicit guidance on when to use this tool versus session.continuity or memory.create, nor any exclusions.

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