surfmeter_execute_destructive_action

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds the crucial confirmation requirement and specifies the source of the action, going beyond what annotations state. No contradictions with annotations.

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?

A single, front-loaded sentence with zero redundancy. It states the purpose, the source, and the critical warning efficiently. Perfectly concise for the information conveyed.

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?

Given there is no output schema and a nested params object, the description lacks essential context: what to put in params, how to identify the correct action_id, and what the return value looks like. The warning to confirm targets is good, but the lack of parameter explanation makes the tool incomplete for correct 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 explain the parameters. It only implies action_id comes from search_actions but does not clarify its format or the purpose of the params object (nested, with arbitrary properties). This leaves the agent guessing about how to fill params and what action_id looks like.

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 states a specific verb ('execute') and resource ('destructive Surfmeter action') and explicitly ties the action to surfmeter_search_actions, distinguishing it from read/write sibling tools. It's unambiguous about what the tool does.

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?

It gives clear guidance to confirm targets and consequences before execution, which is essential for a destructive action. It also indicates the action must come from surfmeter_search_actions, implying the correct prior step. It doesn't explicitly list alternatives, but the 'destructive' qualifier and sibling names make the intended use obvious.

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