get_seller_deals

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

With no annotations provided, the description carries the burden of indicating behavior. 'Get' implies a read-only operation, and the return of deal IDs is stated. However, it adds no detail about pagination, error handling, or whether the address must be exactly the seller, making the transparency adequate but minimal.

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, clear sentence with no redundant words. It efficiently communicates the tool's purpose and scope.

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 simple tool with one parameter and no output schema, the description adequately specifies the return content (deal IDs) and the filtering condition. It is complete enough for an agent to understand what the tool returns and when to invoke it.

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 description for the address parameter ('Seller wallet address') fully aligns with the tool description's use of 'seller'. Since schema description coverage is 100%, the tool description adds no additional parameter detail, matching the baseline for high 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?

The description clearly states the tool's function: retrieving all escrow deal IDs for a given seller address. It uses a specific verb ('Get'), identifies the resource ('escrow deal IDs'), and specifies the filter (address as seller), which distinguishes it from sibling tools like get_buyer_deals.

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 when to use the tool (when you need deals where the address is the seller) but does not explicitly mention alternatives or exclusions. Sibling tools like get_buyer_deals are not referenced, so guidance is only implicit.

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