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

Annotations already declare readOnly, idempotent, non-destructive, and non-openWorld, so the safety profile is covered. The description earns credit beyond that by spelling out the full status state machine (draft until email confirmation, then open/receiving/reviewing/awarded/expired/cancelled, demo for demo requests), which is real behavioral context an agent cannot get from the structured fields.

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?

A single sentence, front-loaded with the resource and its primary output before the status enumeration. It is dense but every clause carries information; the long parenthetical is slightly heavy but justified by the status vocabulary it supplies.

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?

With no output schema, the description is the only source for return semantics, and it covers all four returned values plus the full status vocabulary. Combined with annotations handling the safety profile, an agent has everything needed to call and interpret this read-only tool.

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 parameters carry their own descriptions (access_key provenance and request_id pattern example), so the schema does the heavy lifting. The description adds nothing about parameter format or acceptable values; baseline 3 is appropriate.

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 (returns) and resource (a request's status) and enumerates the exact fields returned: status, offer count, invited-business count, and dashboard link. That is far clearer than the bare title. It does not, however, explicitly contrast itself with siblings like get_bids or get_request_form, so an agent still infers the boundary.

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?

There is no statement of when to call this versus alternatives such as get_bids or get_request_form, nor any stated precondition beyond the schema-required access_key. The lifecycle parenthetical hints at polling after create_request, but usage is left entirely to inference.

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