get-lineage-by-name

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

No annotations and description does not disclose behavioral traits such as read-only nature, depth parameter effects, or return format. The agent is left to infer behavior from the name and schema.

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?

Single sentence is efficient but omits essential details about depth parameters and behavior. Could be more informative without being verbose.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It does not explain depth defaults, return type, or differentiation from similar tools.

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 50% (entity and fqn have descriptions, upstreamDepth and downstreamDepth do not). The description adds no additional meaning for the undocumented parameters, missing a chance to explain depth semantics.

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 verb 'Get' and resource 'upstream and downstream lineage for an entity by FQN'. It specifies the key input (FQN), but does not distinguish from sibling 'get-lineage' which may have similar purpose.

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 vs alternatives like get-lineage or lineage-impact. The description lacks context for selection.

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