readMessages

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

Discloses destructive default (clear buffer), limit capability, and return status field. However, no annotations provided, and description lacks rate limits, error handling, or prerequisites for subscription.

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?

Single sentence with front-loaded action, clear structure using semicolons for details, no redundant words.

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?

Despite no output schema or annotations, description covers key behaviors, parameter effects, and return field. Missing details on invalid subscription or empty buffer, but contextually sufficient given sibling tools.

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 baseline 3. Description reinforces parameter purposes (limit for recent N, clearAfterRead for buffer clearing) but adds no new constraints or formats beyond schema.

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?

Description clearly states the verb '读取' (read) and resource '指定订阅已积累的消息' (accumulated messages of specified subscription), distinguishing it from sibling tools like startSubscription, stopSubscription, and listSubscriptions.

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 explains default behavior (clearAfterRead=true) and alternative (clearAfterRead=false) but does not explicitly contrast with streaming subscription tools (e.g., subscribe_*) or state when not to use this tool.

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