delete_measure

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the deletion is permanent or reversible, whether dependent visuals or other measures are affected, what permissions are required, or what error conditions may arise. Only the intent to delete is communicated.

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 fluff—every word serves the primary purpose. It is efficient, though it could carry additional useful detail without becoming verbose.

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 destructive 3-parameter tool with no annotations, no output schema, and a large sibling toolset, a one-line description is insufficient. The agent lacks information about return values, side effects, prerequisites, and distinctions from similar delete tools, making the description incomplete for safe invocation.

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%, so the description must compensate; it maps 'name' to the measure and 'table' to the containing table, but this merely restates the parameter names without adding detail on identifier formats, scoping, or uniqueness. sessionId is left entirely unexplained, leaving a significant semantic gap for a required parameter.

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 a specific verb ('Delete'), a clear resource ('measure'), and scope ('from a table'), which precisely states the tool's function. It distinguishes itself from sibling tools like add_measure, update_measure, move_measure, and delete_calculation_item by naming the operation and the target object.

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 delete_template_measure or delete_calculation_item, nor any prerequisites, exclusions, or context for choosing it. It is a bare operation statement with no usage rules.

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