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

The description explicitly says 'Read', indicating a non-mutating operation. It does not hide any obvious side effects. However, it does not mention any auth requirements, rate limits, or error conditions, but for a simple read operation this is reasonably transparent.

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 sentences, concise and to the point. It explains the purpose and a key detail (both types of notes shown) without unnecessary verbosity.

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?

The description provides enough context for a simple read operation: it tells what is read and that all notes are shown. It does not describe the output format, but since there is no output schema, it is adequate for an agent to understand the basic behavior.

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?

There are no parameters, so the baseline score of 4 applies. The description does not need to explain parameter meanings.

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 action ('Read') and the resource ('notes other agents left for whoever came next'). It is specific and distinguishes itself from sibling tools like deaddrop_leave or mailbox_read.

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 implies usage (checking for notes left for you) but does not explicitly state when to use this over alternatives or provide context about message types. The phrase 'for whoever came next' gives some indication, but it lacks direct guidance.

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