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

The annotations already declare readOnlyHint and idempotentHint, and the description adds extra behavioral context: it is 'free, rate-limited only' and not a live Reddit call, which informs cost and latency expectations. It also discloses the account requirement and the reddit_search subreddit field quirk, going well beyond the structured annotations.

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 packed with useful information and front-loads the core purpose in the first sentence. Subsequent sentences add details about output fields, an edge case, and constraints. It is slightly long with the parenthetical signup link, but every sentence earns its place and it remains focused.

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?

Despite having no output schema, the description outlines the key return fields (sources, paused state, tags, record counts, today's arrivals) and clarifies the reddit_search subreddit quirk. It also notes authentication requirements and rate-limit behavior, making it complete for a zero-parameter list 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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter details (since none exist), but it does explain what the response contains, which helps the agent interpret output rather than input. There is nothing more to add for parameters.

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+resource: 'List the Watchers configured for your organization,' immediately establishing what it does. It distinguishes from siblings by noting 'the same ones the dashboard manages' and clarifying that reddit_search watchers correspond to Keyword Monitor entries, which sets it apart from other listing tools like keyword_monitor_list.

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?

It provides clear context: use it to see organization watchers, their sources, paused state, tags, and counts. It warns that it is 'NOT a live Reddit call,' implying it is not for real-time data, and notes a free Prowlo account is required. However, it does not explicitly name alternative tools for live Reddit data, so the exclusion is implied rather than stated.

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