sigma_swap_data_model_sources

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

The description adds no behavioral context beyond the basic 'swap' operation. Annotations already indicate non-read-only and non-destructive, but nothing is disclosed about effects on dependent elements, required permissions, reversibility, or side effects.

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 short sentence with no filler, making it concise and front-loaded. However, it is under-specified for a tool with an open-ended body schema and no additional guidance, so brevity borders on insufficiency rather than effective conciseness.

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?

Even though an output schema exists, the tool involves an unstructured 'body' object and swapping semantics that are not explained. The one-line description does not provide enough context for correct invocation, especially with numerous sibling swap tools and related operations.

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 schema has two parameters with zero description coverage; the body parameter is an open additionalProperties object with no explanation, and the description never mentions how to construct or use either parameter. The description does not compensate for the low schema coverage.

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 action verb 'Swap' and identifies the resource as 'data sources for a data model,' which clearly distinguishes it from sibling swap tools targeting workbooks, reports, or templates. However, it does not elaborate on the scope or nuances of what swapping entails.

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 alternatives such as sigma_swap_workbook_sources or sigma_swap_report_sources. No exclusions, prerequisites, or situational context are provided, leaving the agent to guess.

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