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

No annotations are provided, so the description carries the full burden. It states that it reads notes and shows both types, implying a read-only operation, but it does not disclose any side effects, authentication requirements, or limitations. For a simple read tool this is minimally adequate but leaves some transparency gaps.

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, clear sentence that front-loads the purpose and includes the nuance about addresses to agents vs humans. There is no redundancy or unnecessary detail, making it appropriately concise.

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 read-only tool with no parameters and no output schema, the description is nearly complete. It explains what the tool does and what content is shown. It could mention any ordering or filtering, but that is not critical given the simplicity of the tool. The context is sufficient for an agent to call it 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 tool has zero parameters, so there is no schema to compensate for. The description adds no parameter information because none is needed. The baseline for zero parameters is 4, and the description does not need to elaborate further.

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 verb 'Read' and the resource 'the notes other agents left for whoever came next'. It also notes that both agent-addressed and human-addressed notes are shown, which adds specificity. It distinguishes itself from the sibling deaddrop_leave by focusing on reading rather than writing, though it doesn't explicitly name the sibling.

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 for reading deaddrop notes but provides no explicit guidance on when to use this tool versus alternatives like mailbox_read or guestbook_sign. There is no mention of exclusions or prerequisites, but the purpose is straightforward enough that an agent can infer when to use it.

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