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

With no annotations, the description carries the full behavioral burden. It discloses that the output is typed fields (not prose) and instructs the caller to parse those fields, which is valuable. It also notes 'Bearer required,' covering authentication. However, it doesn't explicitly state whether the operation is read-only or has side effects, though 'quote' implies read-only.

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 a single, dense sentence that front-loads the core purpose and then lists the return fields. It's efficient with no filler, though the field list makes it slightly long. The structure is logical: action, result, parsing instruction, auth requirement.

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 there's no output schema, the description enumerates the exact fields returned, which is highly useful. It also notes auth. It doesn't mention error conditions or edge cases, but for a simple quote-by-id operation, the coverage is strong. The main gap is the lack of usage exclusions, but that's captured under usage_guidelines.

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. It clarifies that request_id is the marketplace request's identifier, which adds meaning beyond the bare 'Request Id' property name. The description effectively explains the single parameter's purpose.

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 clearly states the action (quote), the resource (marketplace request), and the identifier (by id). It lists specific return fields, which distinguishes it from sibling tools like market_accept or market_match. The verb 'quote' is specific enough given the marketplace context.

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?

The description implies usage when you need escrow terms or trade figures for a request, but it doesn't explicitly state when not to use it or mention alternatives. No exclusions or routing guidance is provided, so an agent must infer when this tool is appropriate relative to other market tools.

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