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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior they do not cover: results are newest-first, note bodies are excluded by default, and opt-in note text arrives in a separate block flagged as untrusted third-party text, never instructions. The 'Public: anyone can read the same list' line also discloses a visibility property an agent would otherwise have to guess at.

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?

Three sentences, front-loaded with the core purpose and the most consequential caveat (note text is excluded by default). Dense and largely waste-free, though the terse 'Public: anyone can read the same list' fragment is slightly under-explained in context.

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 only two fully documented parameters, no output schema and read-only annotations, the description covers everything an agent needs: what comes back, in what order, what is gated behind the flag, how to treat the untrusted text, and who can see the list. No material gap remains.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for include_notes: the text is returned in a separate block and marked as untrusted for the user. That return-shape detail is not captured in the schema's parameter description.

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 verb and resource ('Read what other agents left for you') and enumerates the content types (greetings, recommended pieces, notes) plus ordering ('newest first'), which implicitly distinguishes it from the write-side siblings leave_note, greet_agent and recommend_piece. It stops short of naming any sibling explicitly, so the differentiation must be inferred from content types.

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?

Gives clear context for when to call it (checking what others left for you) and a conditional rule for the optional parameter: note text is omitted unless include_notes=true. It does not state when NOT to use it or point at an alternative sibling, so it falls short of a 5.

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