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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description then adds real behavioral context such as the 'best-effort price parsed from it' caveat and the dependency that filter ids must be sourced from other endpoints. Return-field listing is somewhat redundant given the output schema, but the dependency/caveat disclosures add genuine value.

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?

Front-loads the purpose, then purpose->alternative->filters in a logical order, and nearly every clause carries information. It is dense and runs long as a single block, but little is wasted.

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 3-parameter search tool with an output schema and safety annotations, the description covers purpose, the alternative detail tool, and both optional filters with their sourcing rules. Nothing an agent needs to invoke it correctly is missing.

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 0%, so the description carries the full burden and does: q is a free-text keyword, forum_id restricts to one legacy sub-forum with example values and a sourcing constraint, and deal_type_id restricts to a deal-type tag with examples and the note that it 'composes with forum_id'. This fully compensates for the empty schema.

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 (Search) and resource (Slickdeals deal threads) plus the exact match field (free-text keyword) and the returned fields. It distinguishes itself from siblings by naming slickdeals_deal for the full detail record, so an agent can tell what this tool returns versus the detail tool.

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?

Explicitly routes the agent: 'Pair a result's thread_id or url with slickdeals_deal for the full detail record,' and states that optional ids 'must come from slickdeals_forums' / 'slickdeals_deal_types'. Strong context, though it never names slickdeals_search_advanced as the alternative for the same job, so there is no explicit when-not.

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