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

The description presents lineage as a retrieval operation ('Full ancestry and descendants'), but annotations declare readOnlyHint=false. This directly conflicts with the notion that the tool only reads existing lineage data, and the description does no work to explain any mutation, side effect, or permission requirement that would justify the annotation.

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 front-loaded sentence with no wasted text. It immediately states the scope of the result and the accompanying generation number.

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?

The tool is structurally simple and has an output schema, so the description need not explain return values. However, the missing usage guidance and the unexplained mismatch with readOnlyHint=false leave important context gaps for an agent deciding whether and how to invoke it.

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 only parameter is agent_id, and schema description coverage is 0%. The description adds no meaning about what the identifier represents, accepted formats, or how to obtain it, leaving the agent with less semantic clarity than the simple parameter name might suggest.

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 gives a specific verb/resource pair: it retrieves an agent's ancestry, descendants, and generation number. This is clear enough to understand the tool's core function, but it does not distinguish it from siblings such as describe_agent or recall, which may also surface relationship or historical data.

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 guidance on when to use this tool instead of alternatives like describe_agent, recall, or verify_artifact. The description states what the tool returns but does not mention prerequisites, exclusions, or the conditions under which an agent should call it.

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