list_watches

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that no credentials are required and names some state fields returned, but it does not explicitly state read-only behavior, pagination, ordering, or error-handling semantics; the 'List' verb weakly implies a read operation.

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 short and front-loads the main list action before listing returned state categories. The fragment 'No credentials' is slightly telegraphic but still useful, and there is no wasted wording.

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 zero-parameter list tool with no output schema, the description gives the main return categories but omits result shape, ordering, pagination, and how it relates to sibling read/status tools. It is adequate but leaves gaps an agent would need to infer.

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?

There are zero parameters, so there is no parameter semantics to document. The schema is empty and the description does not need to compensate for missing 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?

The description uses the verb 'List' with the resource 'persistent searches' and enumerates returned state categories such as baseline state, scan freshness, and errors. It distinguishes the tool from mutation/control siblings like create_watch and pause_watch, though it does not explicitly differentiate it from monitoring_status or search_items.

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 list operation implies its usage, and the phrase 'No credentials' hints at access conditions. However, there is no explicit when-to-use guidance, no exclusion of monitoring_status or search_items, and no prerequisites or routing advice.

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