watchlist_performance

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

No annotations provided. The description only implies read-only ('Gets') but does not disclose auth needs, rate limits, or any side effects. With no annotations, the description should provide more behavioral context.

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 extremely concise (two lines) with no superfluous information. Every word serves a purpose.

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 simple one-parameter tool with an output schema, the description covers the essential action and parameter. It lacks details on error handling or prerequisites, but the existing output schema compensates for return value documentation.

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 description adds meaning to the parameter 'watchlist_name' with the phrase 'Name of the watchlist to analyze', which is not present in the schema (0% coverage). This clarifies the parameter's role beyond just its type.

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 clearly states the action ('Gets') and the resource ('performance metrics for a watchlist'), distinguishing it from sibling tools that list, add, or remove watchlists.

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 tool versus alternatives like 'watchlist_by_name' or 'all_watchlists'. Does not mention prerequisites (e.g., watchlist must exist) or when not to use.

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