Services request quote

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

The description explains the workflow and the fixed-price refusal behavior, which goes beyond the minimal annotations. It does not mention idempotency or repeat-request effects, but the core side effects are reasonably clear.

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 two sentences, direct, and packs essential distinctions and workflow details without unnecessary verbosity.

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 tool with no output schema, the description gives sufficient context about the request lifecycle and edge case (fixed-price refusal). It could mention how to retrieve the resulting seller response, but the sibling tools make that discoverable.

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?

The schema already covers all three parameters with descriptions, so the description adds little extra parameter-level meaning. It does reinforce that scope must conform to the listing's scope schema, but the schema itself already states this.

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 specific action: filing a scope-of-work against a quote-mode service listing. It also explicitly distinguishes this from services_purchase for fixed-price listings.

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 gives explicit guidance on when to use the tool (quote-mode listings) and when not to (fixed-price listings, directing to services_purchase). It also outlines the expected flow: seller responds with price + ETA, buyer has 24h to accept.

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