surfmeter_execute_read_action

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's read-only framing adds little safety information beyond structured data. It does add a useful provenance constraint: the action must come from surfmeter_search_actions, which is the main behavioral value.

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 sentence with no filler. It front-loads the core purpose and usefully names the source tool without wasting words.

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 an execute tool with an unrestricted params object, no output schema, and no parameter documentation, this description is too thin. An agent does not know how to construct params, whether to call surfmeter_describe_action first, or what the response will contain. The pipeline hint helps but leaves essential execution details unspecified.

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, but it only gives indirect context for action_id by mentioning the action comes from a search. It does not explain the required action_id format or the params object semantics, which are entirely unconstrained in the schema.

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 states a specific verb ('Execute') and resource ('read-only Surfmeter action'), and explicitly ties the action to the output of surfmeter_search_actions. This clearly differentiates it from the write and destructive execution siblings.

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 phrase 'returned by surfmeter_search_actions' provides clear usage context and implies this tool should be called after a search. It does not explicitly state exclusions or alternatives, but the read-only qualifier plus sibling names make the intended scope reasonably clear.

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