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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the underlying endpoint ('GET /deals/search'), which is marginally useful; it says nothing about match semantics (substring vs exact), result ordering, or what happens with very short/ambiguous names.

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 short sentences with no waste and the purpose is front-loaded. The trailing endpoint reference is low-value for an agent but not harmful; the tradeoff is that terseness comes at the cost of guidance.

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 read-only search with full schema coverage and no output schema, the essentials are present. However, nothing is said about result shape, pagination beyond the schema's next_page hint, or behavior on zero/many matches, leaving gaps an agent would want to know.

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%, so name, page, perpage and includes are all documented in the schema, including the useful 'pass the previous reply's next_page' instruction. The description contributes only 'by name', which is already in the schema – baseline 3 applies.

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?

States a specific verb ('Find') and resource ('deals') and the matching field ('by name'), which distinguishes it from get_deal (single record by id) and list_deals (enumeration). It never names a sibling explicitly, so differentiation is inferential rather than stated.

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?

Usage is only implied: search when you know part of a deal name. There is no explicit 'use this instead of list_deals when...' guidance, no note about behavior when the name matches many deals, and no fallback if no match is found.

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