erinys_lineage

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

With no annotations, the description carries the behavioral burden. It discloses the traversal algorithm (following provenance.parents, falling back to distilled_from) and the 'lineage-complete' chain construction, which adds meaningful context. However, it does not mention depth limits or cycle handling.

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 two sentences and fairly efficient, though the opening phrase 'VMG Provenance Visibility' is vague and not front-loaded with the most critical information. Still, every sentence 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?

An output schema exists, so return format is covered. However, the description does not explain the impact of max_depth, behavior on missing provenance, or invalid IDs, leaving gaps for a traversal tool. It is adequate but not fully complete.

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 schema provides only names and defaults (id, max_depth) with zero description coverage, yet the description does not explain what these parameters mean or how they affect the traversal. The names are somewhat self-explanatory, but the description fails to compensate for the missing schema descriptions.

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 clearly states that the tool traces the lineage of a memory in the ancestor direction using provenance.parents or distilled_from, with a specific verb ('traces') and resource (memory provenance). It is distinguished from siblings by focusing on ancestry, though it does not explicitly name alternatives.

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?

The description implies usage for retrieving ancestor chains of a memory, but it does not provide explicit guidance on when to use this tool versus siblings like erinys_traverse or erinys_get, nor does it mention 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.