watchlist_list

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

With no annotations, the description must disclose safety and side-effect properties. It simply states the listing action without explicitly stating that it is read-only, whether it requires any permissions, or how it handles an invalid account. It also lacks details about pagination or response structure, which are not provided elsewhere since the output schema exists but is not described.

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 a single sentence with no filler. It immediately states the action and resource, earning high marks for conciseness.

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?

The tool has an output schema, so return values are covered, but the description lacks context about the watchlist lifecycle, the meaning of 'persistent,' and how this tool fits with watchlist_create/update/delete. Given the simplicity, it's partially complete but misses important surrounding information.

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 'account' parameter has no schema description (0% coverage). The description says 'an account's,' which gives minimal context, but it does not specify the expected format (ID vs name), required permissions, or examples. This does not compensate for the schema gap.

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 a specific verb ('List') and resource ('watchlists') scoped to 'an account's persistent' variant. This distinguishes it from sibling tools like watchlist_get (single watchlist) and watchlist_create. Clear and specific.

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 is provided on when to use this tool versus watchlist_get, watchlist_quotes, or other watchlist tools. It does not state whether to call this before modifying watchlists, nor does it mention any alternatives. The only implied usage is from the action itself.

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