provenance__lineage

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the operation is read-only, requires specific permissions, has rate limits, or what happens on missing agent_id. The description only states what is returned, not side effects or constraints.

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 a single sentence, but it includes a misleading header-like prefix '[provenance — genesis certificates, lineage, recalls]' which may confuse the tool's scope. The core sentence is concise but front-loads irrelevant context.

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 the low complexity (1 parameter, no nested objects), the description adequately specifies what the tool returns: full ancestry, descendants, and generation number. However, lacking output schema, it does not explain response structure, but the description is sufficient for an agent to understand basic purpose.

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 0% (no parameter descriptions in schema). The description does not add meaning to the single parameter 'agent_id' beyond its name. It does not specify format, constraints, or how it is used in the lineage resolution. The agent must assume it is the identifier of the agent whose lineage is requested.

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 the tool's purpose: retrieving full ancestry and descendants of an agent plus generation number. It distinguishes from sibling tools like provenance__describe_agent (which likely gives current info) and provenance__list_records (general records). The verb 'get' is implied, and the resource 'lineage' is explicit.

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?

No guidance on when to use this tool versus alternatives such as provenance__describe_agent or provenance__list_records. The description does not specify prerequisites or typical use cases, leaving the agent to infer from the tool name.

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