listDeals

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states that the tool lists deals with filtering, but omits important behaviors like pagination (cursor, limit, offset), sorting, field selection, default result sizes, or whether it returns full or partial deal objects.

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 short, front-loaded phrase with no wasted words, but it is under-specified. A second sentence about pagination or scope would make it more useful without adding significant length. It's concise yet lacks structural completeness.

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 the tool has 10 parameters, no output schema, and no annotations, the description is far too minimal. It does not explain return value format, pagination behavior, default limits, or filter semantics, making it difficult for an agent to use the tool correctly without additional external knowledge.

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?

All 10 parameters have schema descriptions, so schema coverage is 100%. The description's phrase 'with filtering' adds little beyond what the schema already documents, and it does not clarify filter combination logic or pagination mechanics, justifying the baseline score of 3.

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 says 'List deals with filtering', which clearly identifies the verb (list), the resource (deals), and hints at the filtering capability. It distinguishes from getDeal (singular) but does not explicitly differentiate from other list tools, and 'with filtering' is somewhat generic.

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 such as getDeal for a single deal or other list tools. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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