watchlist_list

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

Annotations declare readOnlyHint=true, and description confirms no side effects. Adds useful behavioral detail about returned fields (name, type, item count, baseline). Does not contradict annotations.

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 sentences, no extraneous content. First sentence describes output; second provides usage examples. Efficient and front-loaded.

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?

Good for a read-only list tool with optional filters. Covers purpose and usage well. No output schema, so description could mention the exact fields returned, but it names the key fields. Acceptable completeness.

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 60% (2 of 5 parameters lack descriptions). The tool description does not add any parameter information. Schema does most of the work, so baseline 3 is appropriate; description could have clarified filter behavior.

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?

Clear verb+resource: lists saved tracking lists with specific attributes (name, type, item count, baseline). Example user queries like 'what am I tracking' make purpose obvious. Does not explicitly differentiate from sibling watchlist tools, but context is sufficient.

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?

Explicitly states when to use with example queries: 'Use when the user asks...'. Provides clear context for invocation. No mention of when not to use or alternatives, but guidance is strong.

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