move_measure

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

With no annotations, the description carries full burden. It discloses key behaviors: DAX references remain unaffected, all associated attributes travel, and it explains the deep clone mechanism and TOM constraint. This goes beyond a simple operation description and provides critical implementation details.

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 front-loaded with the core action and packs significant behavioral context into two sentences. The second sentence is a dense enumeration but still earns its place. Slightly technical, but no redundancy.

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 move operation with no output schema, the description covers the operation's effect on references and attributes, and notes the TOM constraint. It lacks explicit error conditions or prerequisites, but given the tool's simplicity, it is fairly complete.

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 description does not add parameter-level detail beyond the schema. The schema already describes 'measure' and 'targetTable', but 'sessionId' is undefined and the description offers no guidance on parameter values, formats, or relationships. With 67% schema coverage, the description should compensate, but it doesn't.

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 identifies the operation ('Move a measure to another table'), specifies the resource (measure) and the action (move), and distinguishes it from siblings like update_measure or delete_measure by focusing on re-homing and preserving DAX references.

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 implies when to use this tool (reorganizing measures across tables) and explains the impact on DAX references, but it does not explicitly state alternatives or when not to use it. The 'when' is clear, but exclusions are absent.

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