sigma_list_data_model_lineage

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context beyond the action itself, such as pagination, permissions, or lineage scope, but there is no contradiction and the tool is a simple read operation.

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, direct sentence that front-loads the action and object. There is no wasted wording or unnecessary detail, making it highly concise and easy to parse.

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?

For a one-parameter read-only list operation with an output schema and safe annotations, the description is mostly complete. It lacks lineage-specific context (e.g., does it show upstream/downstream? is there depth?), but given the simplicity and available structured data, it is adequate.

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%, so the description should compensate. While 'for a data model' implies the data_model_id refers to a data model, it does not explain the parameter format, required structure, or any additional semantics beyond what the name 'Data Model Id' already conveys.

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 the action ('List') and the specific resource ('lineage for a data model'). It distinguishes from sibling tools like sigma_list_workbook_lineage and sigma_list_report_lineage by explicitly naming the data model resource.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to choose sigma_list_data_model_lineage over sigma_list_workbook_lineage or sigma_list_report_lineage, nor does it describe any prerequisites or context.

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