watchlist_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The parenthetical '(without their secrets)' hints the output strips secrets, which is a small useful note, but it's cryptic rather than disclosure. No mention of pagination, ordering, or what fields are returned for a no-arg list.

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?

Two fragments, extremely short and front-loaded by size, but the brevity comes at the cost of meaning. 'Free' is unclear pricing noise.

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?

Zero-param read tool with no output schema. For a list tool the description should say what a list contains and how it relates to watchlist_get, watchlist_deliveries, and watchlist_create. 'Alerts (without their secrets)' is too thin to call the tool correctly.

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 baseline 4. Nothing to document and the description introduces no confusion about 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 'Your funding-signal alerts (without their secrets). Free.' is a fragment, not a stated action. The name watchlist_list implies listing, but the description doesn't say it lists anything. It gestures at 'alerts' but never states the verb+resource, and it doesn't differentiate from watchlist_get.

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 watchlist_get or the many other siblings. No context, no exclusions.

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