watchlist_summary

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

Description implies a read-only fetch operation, but no explicit statement about side effects or permissions. With no annotations, the description provides minimal behavioral context beyond the action. Could mention that it requires authentication or that it does not mutate data.

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?

Single sentence, no extraneous information. While concise, it could be slightly more structured (e.g., separate the fetch and summarize actions) but overall efficient.

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 core purpose adequately. It explains the action (fetch account page) and the result (summarize tickers/auth). Could mention that the output is a summary object, but not critical.

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?

No parameters exist, so the description does not need to add semantic depth. Schema coverage is 100%, and the description succinctly explains what the tool does without needing parameter details.

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?

Description uses specific verbs ('Fetch', 'summarize') and identifies the resource ('account page', 'visible tickers / auth'). Clearly distinguishes from sibling tools which focus on posts, threads, news, or search.

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 explicit guidance on when to use this tool vs alternatives. Usage context is implied by the tool's purpose (summarizing account data) but no clarifying statements about when not to use it.

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