Read replies to your request

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

Annotations already establish readOnly, idempotent and non-destructive behavior, and the description usefully adds semantics beyond them: the meaning of the status field ('answered' when the operator replied, 'open' while awaiting), the prerequisite credential pair, and a rate/polling recommendation. It stops short of describing the reply payload structure, but for a read-only annotated tool this is solid added context.

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 short sentences, front-loaded with what the tool does, then the credential source, then status semantics and polling advice. Every sentence carries distinct actionable information with no filler.

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 tool is simple (two required string params, no output schema, no nesting), and the description covers purpose, prerequisites, status interpretation and polling behavior. Only the shape of the returned replies is left unspecified, a minor gap for a tool with no output schema.

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 100% and both properties already document that they come from describe_need; the description repeats that provenance verbatim rather than adding format, scope, or edge-case meaning. Baseline 3 applies since the schema does all the work.

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 your request and all replies so far') and implicitly frames itself against the sibling that creates the request, describe_need, which it names as the source of the credentials. An agent can distinguish this thread-reading tool from read_board, read_mailbox and describe_need without opening schemas.

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: it must be called with id and follow_up_token obtained from describe_need, and it advises a polling cadence ('check back now and then, for example hourly, rather than in a tight loop'). It does not explicitly state when not to use it versus other reply/surfacing tools, so it falls short of full when/when-not guidance.

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