slickdeals_forums

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

There are no annotations, so the description carries the behavioral burden. It discloses that the list is refreshed periodically from Slickdeals' own site, that it returns the full legacy sub-forum list, and that q narrows by substring match. For a simple read/list endpoint this is solid, though it does not mention output field details or any pagination/limits.

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 longer than average but every sentence earns its place by adding purpose, sibling differentiation, or usage context. The middle sentence is somewhat dense with em-dashes and comparisons, but it is not padded and the key action is front-loaded.

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 optional-filter list endpoint, the description covers what is returned, how it relates to sibling endpoints, how filter works, and data freshness. With no output schema, it still gives enough context (full list, id-to-name resolution) for an agent to call it correctly. Minor omissions like exact response fields are acceptable at this complexity.

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 the schema fully documents q as a 'Case-insensitive substring filter on name.' The description restates this as 'narrows it to a substring match on name,' adding no new meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 opens with a clear verb+resource statement: 'List every Slickdeals legacy sub-forum.' It further distinguishes itself from the siblings in its domain by naming the coarser-grained categories taxonomy and identifying this endpoint as the discovery mechanism for forum_id used by deal/search/advanced/frontpage endpoints.

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 explicit: it is 'the discovery endpoint for GET /slickdeals/search's forum_id parameter' and 'the way to resolve an id to a name or filter search results by it.' It also explicitly contrasts with GET /slickdeals/categories' 421-entry tag list, telling an agent when this tool is the right choice versus the categories alternative.

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