sigma_list_report_lineage

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

The description adds no behavioral context beyond what the annotations already provide. It does not explain what 'lineage' entails (e.g., upstream/downstream dependencies, depth, pagination) or any side effects. The annotations (readOnlyHint=true, destructiveHint=false) cover read-only safety, but the description itself discloses no additional traits.

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 unnecessary words. It is concise and appropriately sized for a simple list operation.

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 simple schema (one parameter), read-only annotations, and existing output schema, the description is minimally adequate. However, it lacks any explanation of what 'lineage' includes or how it differs from other report-related list tools, so it is not fully complete for an agent unfamiliar with the domain.

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 input schema has one parameter (report_id) with zero description coverage. The tool description does not explicitly explain report_id, its format, or how to obtain it. The phrase 'for a report' implies the ID references a report, but this is not enough to compensate for the missing schema descriptions.

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 'List lineage for a report.' It uses a specific verb ('list') and a specific resource ('lineage for a report'), and it distinguishes itself from sibling tools like sigma_list_workbook_lineage and sigma_list_data_model_lineage by focusing on reports.

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 such as sigma_list_report_sources or sigma_list_workbook_lineage. There is no mention of prerequisites, exclusions, or situational recommendations.

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