sigma_list_data_model_columns

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 covered by structured data. The description only restates the basic behavior and does not add context about large result sets, pagination, or any other behavioral traits. It is consistent with annotations but adds no additional transparency.

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 that directly states the action and scope without extraneous details. It is front-loaded with the verb and object, making it highly concise and effective.

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 is simple, has one required parameter, and an output schema exists. However, the description does not mention the required parameter or any limitations, relying on the schema and tool name to provide that information. For a simple read-only list operation, this is marginally adequate but could be improved by mentioning the data_model_id dependency.

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, data_model_id, with no description. The tool description does not mention the parameter at all, so it provides no compensation for the 0% schema coverage. The agent must infer the parameter from the name and schema structure.

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 uses the specific verb 'List' and clearly specifies the resource: 'all columns across all elements in a data model.' This distinguishes it from sibling tools like sigma_list_columns_for_table, which targets a table, and sigma_list_workbook_columns, which targets a workbook.

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 clearly states the function but does not mention when to use it over alternatives, nor provide any exclusions or references to sibling tools. The use case is implied by the wording, but no explicit guidance is given.

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