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

Annotations already declare readOnlyHint and openWorldHint, so the read-only nature is covered. The description adds genuine behavioral context beyond that: its role as forum_id discovery/resolution and its distinctness from the categories taxonomy. It omits any note on result shape/size or rate limits, but the annotation already carries the safety profile.

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-loaded with what the tool is, then the usage/routing guidance, then the param. Dense but each clause earns its place. Minor: the parenthetical cross-references to four sibling tools make the middle sentence heavy.

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?

An output schema exists, so return values need not be explained. The description covers purpose, when/when-not vs the sibling taxonomy, the param, and the downstream forum_id linkage—everything an agent needs to call it correctly.

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 must carry the parameter burden, and it does: 'Optional q substring-filters by name' explains both the optionality and the filtering semantics (substring match on name). Slightly terse but adequate for a single param.

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 resource ('Slickdeals' full legacy sub-forum list') with concrete examples (Hot Deals, Coupons, Freebies), so the agent knows exactly what it returns. It also differentiates from the sibling slickdeals_categories by calling itself a 'different, coarser-grained taxonomy'.

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 states when to use it: as the discovery source for slickdeals_search's forum_id param and to resolve forum_ids returned by slickdeals_deal/slickdeals_search_advanced/slickdeals_frontpage into names. It also names the alternative taxonomy (slickdeals_categories), giving a clear routing decision.

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