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

The annotations (readOnlyHint, openWorldHint, destructiveHint) already indicate a safe read operation, but the description adds crucial behavioral context: the possibility of delayed email replies, the meaning of 'offered' as pending, and the polling rate constraint. This enriches the agent's understanding beyond the annotation hints.

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, front-loaded with the core function and usage trigger, then adds necessary behavioral nuance. No redundant content; every clause earns its place.

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 there is an output schema (present but not shown) and the description clarifies status semantics and polling behavior, the tool is fully specified for correct invocation. Nothing critical is missing—the agent knows what to expect and how to interpret results.

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 the schema clearly documents introduction_id as returned by demand.request_introduction. The description doesn't add new parameter meaning; it only uses the parameter in context. Baseline of 3 is appropriate since the schema carries the burden.

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 states a specific verb (check/read) and resource (introduction seller reply), and explicitly links to the creation tool demand.request_introduction, distinguishing it from siblings like demand.ask. It clearly tells the agent what operation is performed.

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 gives an explicit trigger ('when the user asks whether the dealer got back to them'), explains the status lifecycle (offered to accepted/declined/expired), and provides behavioral guidance on treating 'offered' as pending and not polling faster than once a minute. This covers when and how to use it, and implicitly advises against over-polling.

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