set_collision_thresholds

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

Annotations confirm this is a destructive action (destructiveHint: true) and that it is not idempotent. The description adds the constraint about policy maxima, which is important operational detail. However, it does not detail error responses or return formats.

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?

It is a single, direct sentence that avoids fluff and is highly effective at conveying the core function and constraint.

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 the annotations (destructiveHint=true) and the specific constraints on input values, the description provides sufficient information for an agent to understand the action and its safe execution boundaries.

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 100%, so the schema itself is fully descriptive. The description provides a high-level explanation of what 'force' and 'torque' thresholds mean in this context, which slightly adds value beyond just the schema definition.

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 the tool's purpose: setting the robot's collision thresholds (force and torque). While it doesn't explicitly name the two parameters (force_n, torque_nm), it describes the resource being modified.

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 provides a key constraint on input values: 'Values above the policy maxima are rejected.' This clarifies operational limits for safe usage.

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