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

No annotations provided; description is simple and implies a read-only search with no side effects. It does not disclose potential behaviors like pagination, ordering, or limits, but given the straightforward nature, a 3 is appropriate.

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 concise sentences with no wasted words. Efficiently communicates purpose and parameter requirements.

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?

No output schema; description does not mention return format or pagination. With 4 parameters and simple functionality, it is adequate but could be more complete by noting response structure.

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%; the description adds minimal value beyond stating required vs optional. Baseline 3 is correct as schema already explains each parameter.

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 'Search active deals filtered by category', specifying the verb and resource. It distinguishes from siblings 'get_deal_by_id' and 'list_active_deals' by requiring a category filter.

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?

States that 'category' is required and other filters are optional, providing clear parameter usage guidance. However, it does not explicitly compare to siblings or specify when to use this tool over 'list_active_deals'.

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