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

Annotations already declare readOnlyHint=true and idempotentHint=true; the description reinforces this with 'Read-only' and adds 'Requires authentication' plus the matching-behavior statement. It adds context beyond annotations without contradiction, though it doesn't disclose pagination or return specifics.

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 short and front-loads the core purpose. Every sentence adds scope, filter guidance, safety, or usage. The minor redundancy with annotations (Read-only) does not hurt.

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?

It covers what the tool does, who it's for, available filters, read-only behavior, and authentication. With no output schema, it doesn't describe the return format, but the schema covers parameter constraints. Given the complexity, this is mostly complete but leaves some param-to-filter mapping to the agent.

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 0%, so the description must compensate. It names filter groups (category, location radius, budget range, urgency) that map roughly to category_id, radius_km/lat/lng, min/max_budget, and urgency, but it doesn't describe individual parameters or their constraints. This is helpful but incomplete for a 9-parameter tool.

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 uses a specific verb ('list') and resource ('open quote requests'), scoped to the authenticated provider's capabilities and service area. It clearly distinguishes this from siblings like get_my_requests or request_quote by positioning it as the tool to find work to quote on.

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 explicitly says 'Use this to find work to quote on', giving clear intended context. However, it does not name alternatives or provide when-not-to-use guidance, so it stops short of full exclusion guidance.

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