Get Watchlist

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

Annotations already provide readOnlyHint=true, and the description complements this by adding session behavior (auto-acquired, auto-releases after idle), which is useful operational context. No behavioral traits are contradicted, and the session disclosure adds value beyond 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?

The description is a single, front-loaded sentence that conveys the purpose and session requirement without redundancy or fluff. Every word earns its place, making it highly concise and well-structured.

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 single-parameter getter with no output schema, the description is sufficiently complete: it states the return type (contracts), the required input (watchlist ID), and the session prerequisite. Missing details like error handling are not essential for this simple tool, and the lack of explicit sibling differentiation is a minor gap.

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 input schema describes the only parameter 'id' as 'Watchlist ID', and the description reinforces this with 'by ID'. Since schema coverage is 100%, the description adds no additional meaning beyond what the schema already provides, aligning with the baseline score of 3 for fully covered 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 clearly states a specific verb ('Get') and resource ('contracts in a specific watchlist') with a scoping qualifier ('by ID'), which distinguishes it from the sibling tool 'get_watchlists' (plural) that likely lists watchlists. This is a precise and unambiguous purpose statement.

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?

The description provides clear context: it is for retrieving contracts from a single watchlist using its ID, and it notes the brokerage session requirement. It does not explicitly mention the alternative 'get_watchlists' for listing all watchlists, but the singularity of 'specific watchlist' implies the appropriate use case, making it clear enough without exclusions.

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