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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses important behaviors: caching (~5 min), non-liveness, unsampled subs sorting last, the available:false success shape with trackingSince and a don't-retry warning, and size-band floors such as the 10,000-member floor and ≥50 members gained requirement. This is rich behavioral context that annotations alone do not provide.

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 dense but front-loaded with the most important distinction (not a live Reddit call) and purpose. Every major clause adds operational value, such as caching, success-shape warnings, and account requirements. The main downside is that the long parenthetical-heavy metric explanation could be easier to parse, and the final 'call it to get a signup link' phrasing is slightly ambiguous.

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 read-only ranked-list tool with no output schema, the description covers the important invocation concerns: what data is used, how metrics are calculated, freshness, caching, account requirements, and how to respond to the not-yet-available fastest-growing case. It does not explicitly describe the full return record shape, but enough is conveyed to select and safely invoke the tool.

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 low (33%), but the description compensates for the key parameters: it explains metric values in detail, including what each ranking means and edge cases, and explains size band behavior with floor rules. 'limit' is not described in prose, though its min/max/default constraints in the schema plus the obvious meaning of the name make it reasonably inferable.

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 specific verb-like resource: 'Ranked lists from Prowlo's tracked catalog' and immediately distinguishes itself with 'NOT a live Reddit call.' It names the exact metrics (largest, most-active, fastest-growing) and optional size bands, so an agent can clearly understand what this tool produces and how it differs from live or search-oriented siblings.

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?

The description gives concrete when-to-use context: 'Good for browsing a category cold or benchmarking a candidate's growth30d against the field.' It also names follow-on alternatives explicitly: 'vet picks with catalog_get_subreddit, then watcher_create.' It further clarifies that this is cached, free, not metered, and requires an account, helping an agent choose based on cost and freshness expectations.

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