Get Watchlists

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds valuable context about session management: the brokerage session is auto-acquired and auto-releases after idle. This goes beyond the annotation without contradiction, explaining a key behavioral trait.

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 two sentences long and front-loaded with the core action ('List saved watchlists'). The second sentence adds necessary session context. Every word earns its place; no filler.

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 tool with no parameters and no output schema, the description covers the essential action and a critical requirement (brokerage session). It does not describe the return format, but for a simple list tool this is acceptable. The sibling 'get_watchlist' likely provides more detail for single-item retrieval, so the context here is sufficient.

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 has zero parameters, so per the rubric the baseline is 4. The description does not need to explain parameters since there are none, and the schema provides no parameter details to supplement.

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 uses the specific verb 'List' with the resource 'saved watchlists,' clearly stating the tool's function. It does not explicitly differentiate from the sibling tool 'get_watchlist' (singular), but the plural form implies listing multiple watchlists, which provides reasonable purpose clarity.

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 mentions a prerequisite (brokerage session) but does not provide guidance on when to use this tool versus alternatives like 'get_watchlist' (singular). There are no exclusions or alternative tool references, so usage context is missing.

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