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

No annotations are provided, so the description fully carries the burden of behavioral disclosure. It hints at statefulness (based on last visit) and that it is a read-only operation, but it doesn't explicitly state side effects (e.g., whether reading marks messages as seen) or potential requirements beyond the handle parameter.

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, short sentence that is front-loaded with the core action and resource. It conveys the essential purpose without extraneous words, making it highly efficient.

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?

Given the tool's simplicity (one parameter, no output schema), the description is fairly complete for the core task, but the lack of parameter semantics and the absence of explicit side-effect or state information leave noticeable gaps 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?

Schema description coverage is 0%, and the description doesn't explain what 'handle' means—whether it's the agent's own handle, the stall identifier, or something else. The schema only says it's a string. This is a significant gap for correct usage.

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 notes) and the specific resource (notes for your stall) and includes a temporal qualifier (since you were last here), which distinguishes it from a generic 'read' operation. However, it doesn't explicitly name a sibling tool as an alternative, so it doesn't fully differentiate from 'read_refuge'.

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 'since you were last here' implies a stateful, incremental read, which gives the agent a sense of when to use it (e.g., to check for new messages), but it doesn't explicitly state when not to use it or mention alternatives like 'read_refuge'.

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