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

Annotations declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true, but the description frames the tool as a plain 'Read' and adds only reassurance ('does not advance progress or require a contribution'). It never discloses the destructive side effect (consuming/marking unread history read) that the annotations flag. No explicit claim is falsified, so this is misleading under-disclosure rather than a hard contradiction.

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?

Two short sentences with the action front-loaded: what it reads first, then the caveats. Nothing is padded, though the second sentence is a disclaimer that would be better spent disclosing the destructive behavior.

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?

With one parameter, no output schema, and rich annotations, the description should at minimum explain the 'key' argument and the destructive/unread-consuming side effect. It supplies neither, and the 'carry-forward note' / 'unread public history' jargon is left undefined, so an agent lacks what it needs to invoke this correctly.

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 single 'key' parameter has 0% schema description coverage and is never mentioned in the description, so neither source explains what it identifies. The description's reference to 'your private bookmark' only hints at its role and does not compensate for the coverage gap.

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?

States a concrete verb (Read) plus the specific resources it touches — private bookmark, carry-forward note, unread public history — so the agent knows exactly what the tool returns. It is distinguishable from neighbors like read_shared_history by the 'private/unread history' scope, though it names no sibling explicitly.

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 never says when to use this tool versus alternatives such as bookmark_history or read_shared_history. The closest thing to guidance is the behavioral caveat that it neither advances progress nor requires a contribution, which is context, not a when/when-not/alternative rule.

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