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

ReadOnlyHint, openWorldHint, and destructiveHint=false already tell the agent the tool is safe and stateful; the description adds value by framing it as pollable and clarifying that it can also 'read the reply'. This enriches the annotations with usage context without contradicting them.

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?

Two short, purposeful sentences lead with the core action and follow with the exact usage cue. There is no filler or repetition; every sentence carries useful semantics.

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 one-parameter read tool with an output schema and safe annotations, this description is largely complete. It covers purpose, usage, and the creation relationship, and delegates return format to the schema. The only small gap is not precisely articulating what happens when there is no reply yet, but the openWorldHint covers that.

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 schema has zero description coverage for the single 'introduction_id' parameter, and the description never explicitly restates its role. 'An introduction created by demand.request_introduction' hints at the parameter, but the agent still has to infer that it is the ID to poll. The description does not fully compensate for the missing schema guidance.

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 names a specific verb and resource ('Check whether a seller has answered an introduction') and explicitly ties it to demand.request_introduction, making it distinct from siblings like request_introduction or ask. It immediately tells the agent what this tool is for, with no vague phrasing.

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?

It gives a clear trigger: 'Poll this when the first is whether the dealer got back to them.' That is actionable and situation-specific, though it does not name alternative tools or describe when not to use it. It therefore has clear context but no exclusions or sibling differentiation.

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