act

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the risk profile is largely carried by structured data. The description adds two genuinely new facts: an undocumented cap of 8 actions per call (the schema imposes no maxItems on the array) and that the next state/image is returned. It omits atomicity (all-or-nothing vs. partial execution on failure) and any permission/precondition detail.

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?

Two short sentences, front-loaded with the operation and its limit, then the return behavior. No filler, no restatement of the tool name, and the constraint that matters most appears first.

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, non-idempotent tool with a rich nested union schema, no output schema, and zero parameter documentation, the description is thin. An agent cannot tell from it what observation_id must be, what 'image' toggles, how coordinates map to the screen, or what happens if one action in the batch fails.

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% across a 3-parameter schema containing a seven-variant discriminated union with zero field descriptions. The description covers the 'actions' array only loosely ('up to 8') and says nothing about 'observation_id' (how to obtain or reuse it), the 'image' boolean, coordinate semantics for move_to/move, or the distinction between move and move_to.

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?

States a specific verb and resource: 'Execute ... hardware input actions on a fresh observation', plus a hard constraint ('up to 8'). This clearly separates it from 'observe' (capture) and 'stop' (terminate) without needing to name them, though no sibling is explicitly referenced.

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?

'on a fresh observation' implies an ordering dependency (an observe call must precede this one) but never states it as a rule. There is no explicit when-to-use/when-not-to-use guidance, no mention of batching multiple actions vs. calling repeatedly, and no mention of when 'stop' is preferred.

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