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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile needs no disclosure. The description does add value by enumerating the statuses it reports (confirmed, declined, replied), which is behavioral context beyond the annotations, but it says nothing about error cases, rate limits, or what an unmatched reference yields.

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 compact sentences with no filler, and the purpose question is front-loaded ahead of the parameter hints. The question phrasing is slightly indirect but does not waste 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?

For a simple read-only lookup whose annotations already cover safety, the description supplies the purpose question and clarifies two of the three inputs. The absence of any mention of business_id and of return shape (no output schema exists) are the only meaningful gaps.

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%, so the description must carry the burden. It explains two of three parameters – reference (the value returned by request_quote/book_appointment) and customer_contact (email or phone) – but leaves business_id entirely undefined in both schema and description.

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 frames the tool as a status query ('Has the business confirmed, declined or replied?') and ties it to a previously-submitted request, which combined with the name makes the purpose clear. It names the sibling tools (request_quote, book_appointment) whose reference is the input, giving some differentiation, though it never states the resource being checked explicitly.

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 implies usage context by specifying that the reference comes from request_quote or book_appointment, so the agent knows this is a follow-up call. There is no stated when-not-to-use, no exclusions, and no reference to alternatives among the remaining siblings.

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