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

With no annotations, the description carries the full behavioral burden and does well: it declares read-only behavior, a 48-hour lookback, newest-first ordering, and a row cap. It does not mention permissions or rate limits, so it stops short of the highest transparency level.

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 compact and front-loaded: the primary question (why refusals occurred) comes first, followed by returned fields and operational constraints. Every clause adds useful information with no filler.

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 no output schema and no annotations, the description supplies the key return contents (code, reason, instrument, side, quantity, counts, remediation guidance), time scope, ordering, and limit behavior. An agent has enough to invoke and interpret the tool correctly.

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 coverage is 0%, so the description must compensate, and it does: `taker` is identified as the caller's account, and `limit` is bounded at 500 rows. It does not explain the default limit of 50 or the exact taker identifier format, but the core semantics are covered.

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 resource and scope: refused quotes to the caller's account in the last 48 hours, with the exact fields returned. An agent can immediately tell this is a diagnostic refusal-history query, distinct from sibling quote and status tools.

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?

Usage is implied by the diagnostic framing (why quotes were refused), but there is no explicit guidance on when to choose this over related tools or when not to use it. It lacks sibling routing or prerequisite conditions.

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