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

No annotations are provided, so the description carries the behavioral burden. It does disclose what a call yields—the lineage fields—but it does not state read-only semantics, error behavior, or any lab requirements beyond what the strategy_id schema description mentions.

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 very short with no filler and front-loads the champion field. However, it is a compressed fragment full of undefined domain jargon rather than a well-structured explanatory sentence, so brevity comes at the cost of clarity.

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?

With no output schema, the field list is the only return-value documentation, and it does cover the main response concepts. But terms like @R#, 'levers', and 'user canvas view vs recommended working' are left undefined, and the distinction from sibling get/list tools is not articulated.

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 already provides 100% coverage for strategy_id, including Lab-tab routing and NO_ACTIVE_LAB error details, so the baseline is 3. The main description adds no additional parameter-level meaning beyond that.

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 lists the concrete contents of a lineage query—champion @R#, per-iteration verdicts, levers, converged flag, and canvas comparison—so the target resource is reasonably clear. The 'get_lineage' name supplies the verb, but the telegraphic style and undefined @R# jargon keep it from being fully self-explanatory.

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?

There is no explicit 'use this when' guidance and no mention of sibling tools like list_iterations or get_experiment. The field list implies the tool is for retrieving champion/verdict/lever/convergence lineage data, but the usage context is only implicit.

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