reddit_monitor_list

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

Annotations already declare this a safe read, and the description adds substantial non-derivable behavior: a lapsed subscription yields an empty/paused list rather than an error, and the null semantics of webhook_ids (default = deliver to every active webhook) are spelled out with an explicit warning not to misread it as 'no destination'.

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 core purpose is front-loaded and every sentence carries information, but the capitalized warning about webhook_ids is longer and more emphatic than strictly needed, and the return-shape detail arrives before the alternative-tool pointer.

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?

With no output schema, the description carries the full burden of describing the return payload (per-monitor filter/active state/cadence plus the {used, total, tier} slots object) and it does so, alongside the caveat an agent would otherwise get wrong about null delivery targets.

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?

Zero parameters, so there is no parameter semantics to clarify — baseline 4 applies. The description instead spends its budget on the shape and meaning of returned fields, which is appropriate for a no-arg call.

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 and resource ('List every monitor on the caller's account') and enumerates the returned fields (filter, active state, cadence, slots), which distinguishes it from siblings like reddit_monitor_health and reddit_monitor_deliveries without opening any schema.

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?

Explains the access condition (reading your own list never requires an active plan), which removes a real gate for the agent, and routes the agent to reddit_monitor_deliveries when it needs resolved delivery targets. It lacks an explicit when-not-to-use statement, but the context provided is concrete.

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