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

Description is consistent with readOnlyHint, idempotentHint, and destructiveHint (false). It adds business context about the seller's obligations but does not contradict annotations. The read-only nature is not explicitly stated but is implied by 'list' and supported by annotations.

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?

Three compact sentences pack all essential information: purpose, status options, and usage context. No redundancy or filler; every word adds value.

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?

Provides complete situational context: distinguishes from the sibling open-requests tool, explains the fixed-price flow, and mentions the required follow-up calls. An agent can confidently select and invoke this tool without additional clarification.

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 already fully covers all three parameters (cursor, status, page_size) with descriptions and defaults. The description reinforces the meaning of 'active' but does not add substantial new detail beyond what the schema provides, so it stays at the baseline for high schema coverage.

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?

Description clearly states it lists charged threads (sales) the seller owes work on, with pagination. It explicitly contrasts with services_list_open_requests for fixed-price vs. quote-based listings, making its purpose unambiguous.

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?

Provides explicit guidance on when to use (seller-side fixed-price purchases) and explains the meaning of the 'active' status. Also indicates the expected follow-up actions (services_start_work, services_submit_deliverable), giving a complete usage picture.

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