list_watch_rules

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

No annotations are provided, so the description carries the full burden; 'List' implies a read, and the GET path reinforces that, but it says nothing about pagination, result limits, or what 'short' vs full detail returns. With no annotations and no behavioral disclosure, this is a significant gap.

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?

A single front-loaded sentence with no waste. The parenthetical endpoint path adds minor orientation value rather than bloat.

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, but the tool has an undocumented optional parameter and zero annotations for a query that presumably requires account scoping. The description is too thin for an agent to call it correctly with confidence.

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 coverage is 0% and the description never mentions the 'detail' parameter at all, so an agent gets no meaning for its default 'short' value or what other values are acceptable. The description does not compensate for the total lack of parameter documentation.

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 your standing watch rules'), making the operation unambiguous and distinguishable from create_watch_rule and delete_watch_rule. It stops short of fully differentiating from other list-style siblings, but the noun phrase is specific enough.

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?

No guidance on when to use this versus get_situation, create_watch_rule, or the other list tools. The word 'standing' implies persistent rules, but nothing tells an agent when to call it or what prerequisite context exists.

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