open_gripper

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds nothing about the consequences — e.g. whether opening releases a grasped object, what force/limits apply, or what happens on repeat invocation. 'Slowly' is the only behavioral detail, which is thin for a destructive motion command.

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 no filler. It is efficient, though the vague term 'operator-verified safe position' consumes the one clause that could have carried operational meaning.

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 zero-parameter action with no output schema, this covers the basic action, but a destructive, non-idempotent motion command should disclose safety implications (dropped payloads, prior state requirements). The description leaves the agent unable to judge consequences before invoking.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4.

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 ('open gripper') and adds a target qualifier ('operator-verified safe position'), which distinguishes it from close_gripper and cycle_gripper. The concept of 'operator-verified safe position' is never defined, so the destination remains ambiguous.

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?

No guidance on when to use this instead of close_gripper or cycle_gripper, nor any precondition (e.g. whether an operator must have verified the pose first, or whether the gripper must be holding something). The only hint of usage is buried in the phrase 'operator-verified', which is never explained.

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