Snowflake Get Object Lineage

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that lineage is sourced from Snowflake Horizon and covers both upstream and downstream directions, but it does not explain the scope of the traversal, depth limits, or what happens for objects with no lineage.

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?

A single front-loaded sentence with no filler, so nothing is wasted. However, its brevity comes at the cost of substance rather than trimming redundancy.

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 values need not be described. But with 0% parameter coverage, no usage guidance, and a lineage domain that involves traversal semantics, the description leaves an agent without enough to invoke the tool confidently beyond the required object_name.

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 description coverage is 0% across all four parameters, so the description must compensate but largely does not. It only loosely alludes to the 'direction' parameter via 'upstream source and downstream dependent', leaving database, schema_name, object_name format, and the accepted direction values (default 'both' has no enum) undocumented.

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?

States a specific verb ('Retrieve') and a specific resource ('upstream source and downstream dependent object lineage'), and scopes the source system as Snowflake Horizon. It is clearly distinct from a general describe or list tool, though it does not explicitly distinguish itself from the sibling lineage tools (get_column_lineage, discover_schema_lineage).

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 versus the closely related snowflake_get_column_lineage or snowflake_discover_schema_lineage, nor any prerequisites or exclusions. The agent must infer applicability purely from the name.

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