Watch Company

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

Reinforces idempotentHint annotation by stating 'Idempotent — following an already-watched company is a no-op.' Also explains downstream effects (powers watchlist_intelligence, alerts, digest), adding 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?

Three sentences with no wasted words: first sentence states core action, second explains significance, third gives usage context. Front-loaded with key information.

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 toggle tool with good schema and annotations, description covers purpose, parameters, idempotency, and consequences. No output schema required; return values are implied. Complete and self-contained.

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 100%, and description adds meaning: clarifies 'action' default and 'unfollow' behavior, and for 'domain' provides an example and suggests finding domains via `search_companies`. No param info missing.

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 clearly states verb ('add'/'remove') and resource ('company to watchlist'), and distinguishes from sibling tools like 'list_watchlist' and 'watchlist_intelligence' by its mutation action.

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?

Provides explicit when-to-use with example user phrases ('watch this company', 'follow Stripe for me', 'stop watching them'). Lacks explicit when-not-to-use, but idempotency is noted. Sibling tools provide context for alternatives.

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