billz_search_sales

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

With no annotations, the description must disclose behavioral traits. It only states 'Search sales with advanced filters (v3 endpoint)', failing to mention pagination defaults, rate limits, or that the endpoint is read-only. The schema includes page/limit but the description adds no behavioral context.

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, short sentence that is concise and front-loaded with the core action. It is not verbose, but could include additional high-level details without losing conciseness.

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 9 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not mention return format, pagination behavior, or date range implications. The schema partially compensates but the description fails to provide overarching context.

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 has 56% description coverage (5 of 9 parameters documented). The tool description does not add new parameter meaning beyond 'advanced filters'. Since coverage is moderate, a baseline of 3 is appropriate; the description does not compensate for undocumented parameters.

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 verb 'Search' and the resource 'sales', indicating a listing/filtering function. The phrase 'advanced filters' hints at multiple parameters, which is accurate given the schema. However, it does not explicitly differentiate from sibling tools like billz_get_sale_details, which could be misconstrued as similar.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain that this tool is for broad searches with filters, while billz_get_sale_details might be for retrieving a single sale by ID. The description lacks exclusions or contexts.

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