watchlist.rebalance

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

Describes destructive removal but relies on dry_run parameter for safety. No mention of consequences, reversibility, or 'Pro feature' implications (e.g., authentication, rate limits). Without annotations, more detail is needed.

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?

Two succinct sentences with no filler. Front-loaded with action, followed by usage guidance. Every word earns its place.

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?

Covers core functionality and usage well. Lacks output description (return format), but with only three parameters and dry_run, the inference is straightforward. Minor gap prevents a 5.

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 descriptions already fully cover parameters (100% coverage). Description adds minimal context beyond schema, so baseline of 3 is appropriate.

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 it analyzes and removes underperformers based on conviction score or win rate. Distinguishes from sibling watchlist.add and watchlist.list by describing a specific rebalancing 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?

Explicitly suggests using to keep watchlist focused, providing clear context. However, lacks explicit when-not-to-use or mention of alternatives, though no alternative rebalance tools exist.

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