GET /sales (Sale)

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

Adds context beyond annotations: mentions pagination behavior, that multiple values for array items are comma-separated, and a deprecation notice. No contradiction with readOnlyHint=true and destructiveHint=false.

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?

Two sentences effectively convey purpose and key usage notes. Front-loaded with purpose. Could be slightly more concise but generally well-structured.

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?

Despite high schema coverage, the description lacks information about return structure (e.g., fields returned, pagination metadata). No output schema exists, so the description should at least hint at what the response contains. This is a significant gap.

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 100%, and the description repeats that multiple values are comma-separated, adding minimal new meaning. The description does not provide deeper parameter semantics beyond what the schema already conveys.

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 'Listagem paginada de vendas' (paginated listing of sales) and distinguishes from sibling tools like get_sale and create_sale by being a list operation. It also notes it covers both one-off and recurring sales.

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 usage guidance on pagination parameters and a deprecation warning, but does not explicitly specify when to use this tool vs other list tools or alternatives. The context of being a listing tool is implicit.

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