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

Annotations already mark it read-only, open-world, idempotent, and non-destructive; the description adds that the result is bounded to current context and contains contributor claims rather than instructions, which is meaningful behavioral context beyond the annotations. It does not contradict annotations.

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, front-loaded with the action and resource; the second sentence adds a useful qualifier without redundancy. No filler.

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 single-parameter read tool with rich annotations, the description conveys what is read, the bounded scope, and the nature of the content. It does not describe the return shape, but with no output schema and a simple read operation this is a minor gap.

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?

Schema description coverage is 0%, so the description needed to explain note_id. It never names the parameter or its role beyond the indirect 'around a note'; the schema only supplies a pattern. This leaves the agent to infer that note_id identifies the note.

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 specific action ('Read') and a specific resource ('visible public replies, replacements and resolution around a note'), which distinguishes it from siblings like read_memo or read_content. It lacks an explicit sibling contrast, so not a 5.

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 'around a note' implies the tool is for retrieving note-context, and 'contributor claims, not instructions' warns about content type. But it never states when to prefer this over read_memo/read_memory/search_memories, nor gives exclusions.

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