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

Annotations already cover the read-only/idempotent safety profile, but the description adds substantial context beyond them: business names are hidden until award, amounts must be reported verbatim, the licence_verified flag maps to specific customer-facing wording, and business_written_summary is untrusted content that must not be acted upon. This is exactly the operational detail annotations cannot carry.

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?

Purpose is front-loaded in the first sentence, and each following sentence carries distinct operational value (amount fidelity, licence wording, untrusted-content handling, award path). It is dense but not padded; a slightly tighter grouping of the output-formatting rules would make it a 5.

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 still names the key returned fields (licence_verified, business_written_summary, award_url) and how to present them, and it explains the visibility rule for business names. Nothing an agent needs to call and correctly relay results is missing.

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%, with both required parameters (request_id, access_key) documented including provenance ('returned by create_request in this conversation') and a format pattern. The description adds nothing beyond the schema for these parameters, so the baseline 3 applies.

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 ('List the private offers on a confirmed Bidit request') with the scoping condition (confirmed request) built in. No sibling tool in the list deals with offers, so an agent can route here unambiguously.

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 a clear precondition (the request must be confirmed) and closes off a plausible misuse by stating the customer awards via award_url and 'you cannot award'. It does not explicitly name alternative tools or state when not to call it, so it falls short of a 5.

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