sigma_list_workbook_lineage

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description carries little burden for safety disclosure. However, it adds no extra behavioral context such as whether lineage includes upstream/downstream dependencies, pagination behavior, or scoping. The description essentially restates the tool name without revealing any 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 clear sentence with no unnecessary words. It is front-loaded and immediately informs the agent of the tool's core purpose.

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?

The tool has only one parameter and an output schema, which reduces the need for detailed return-value explanations. However, the description lacks usage guidance and parameter clarification, making it minimally viable but with clear gaps. It is not as complete as a well-rounded description would be for a similar list operation.

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%, and the description does not explain the workbook_id parameter. While the parameter name is somewhat self-explanatory, the description does not compensate for the lack of schema documentation by providing details about expected format, requirements, or how it affects the lineage listing.

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 'List data lineage for a workbook' uses a specific verb (list) and resource (data lineage for a workbook), clearly distinguishing it from sibling tools that list lineage for data models or reports. It is precise and non-tautological.

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 is provided on when to use this tool versus alternatives. There are no examples, exclusions, or references to other tools like sigma_list_data_model_lineage or sigma_list_report_lineage. The description only states the basic action.

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