get_lineage

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

With no annotations provided, the description carries full burden. It discloses the response structure (guidEntityMap, relations), parameter options, and defaults. It does not mention permissions or side effects, which is acceptable for a read-only operation implied by 'get'.

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 moderately sized and front-loaded with purpose. It includes a blank line and parameter list, but the section 'This is the most valuable tool...' could be integrated to be more concise.

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 tool has 3 parameters, an output schema (even though not provided in the evaluation), and no annotations, the description fully explains what the tool does, its parameters, and the response structure. It is complete for an agent to select and invoke the tool correctly.

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%, so the description must define parameters. It provides clear descriptions for `guid`, `direction` (with enum values), and `depth` (with default and max). This adds significant meaning beyond the schema.

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 'Get the data lineage graph for an entity' with a specific verb and resource, and explains it traces upstream/downstream data flow. It distinguishes itself from siblings like `get_lineage_by_attribute` by focusing on GUID-based lookup.

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 understanding data flow and calls it 'the most valuable tool.' However, it does not explicitly state when to use alternatives like `get_lineage_by_attribute` or when not to use this tool.

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