watchlist_get

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

No annotations are provided, so the description carries the full burden. It only states the action and identifier types; it does not disclose whether the operation is read-only, what happens for invalid or missing watchlists, or any account-specific requirements. The tool's safety profile is left entirely to inference.

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 delivers the core purpose and a key parameter detail in very compact form, earning every word.

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 description is overly sparse for a tool with two required parameters and no annotations. It fails to explain the role of `account`, offers no guidance on when to use the tool, and does not set expectations for output or errors. The presence of an output schema mitigates some return-value ambiguity, but the missing account context and operational guidance make it incomplete.

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 0%, so the description must compensate. The phrase 'named watchlist or numeric watchlist id' adds meaningful clarification that the `watchlist` parameter accepts either a display name or an ID. However, the `account` parameter remains completely unexplained, and no format or constraints are added beyond what the schema shows.

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 states a specific action ('Get') on a specific resource ('one named watchlist or numeric watchlist id'), which distinguishes it from watchlist_list (list all) and watchlist_quotes (quotes). However, it does not clarify what the returned watchlist contains or how it differs from a simple read of metadata.

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?

There is no explicit guidance on when to use this tool versus alternatives like watchlist_list or watchlist_quotes. The phrase 'one named watchlist' implies a single fetch, but the description does not state prerequisites, exclusions, or alternative scenarios.

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