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

The description adds substantial behavioral context beyond the read-only annotations: it explains the since-based net difference, the edge case of a name added and dropped in between, how added/dropped names carry performance, pending scoring, and a caution that this is a tracked model portfolio, not a recommendation.

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 front-loaded with usage context and effectively structured. It is somewhat lengthy, but each sentence serves a purpose (usage, since behavior, edge case, return semantics, disclaimer), with minimal waste.

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?

Given no output schema and a read-only, idempotent tool, the description fully covers what the return values contain, the difference calculation, edge cases, and the model-portfolio context. An agent has enough information to call it correctly without ambiguity.

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?

With 100% schema coverage, the baseline is 3. The description adds meaning beyond the schema: it clarifies that since is when the user last looked or last updated holdings and that the result is a net difference, which enriches the parameter's semantics. It stops short of covering every nuance, but is above baseline.

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 provides a specific verb and resource: retrieving which stocks were added or dropped from a Quantral strategy's list. It clearly distinguishes itself from sibling get_strategy (current list) and list_strategies by focusing on changes over time.

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?

It states when to use the tool ('when someone already following a Quantral strategy asks what changed') and explains the two modes (with/without since). However, it does not explicitly name the alternative sibling tool (get_strategy) for retrieving the current list, leaving a small gap in exclusions.

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