obsbot_tail2_preset_speed

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

With no annotations, the description carries the full burden. It does add genuine behavioral context by stating writes are 'Readback-verified', which tells the agent writes are confirmed. However, it omits how the dual read/write mode is selected (omit 'speed'?), permission requirements, and whether changing speed affects in-flight gimbal motion.

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?

Three short, front-loaded sentences with no filler; the core action and its effect lead. Slightly terse at the expense of completeness, but nothing is wasted.

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?

No annotations, no output schema, 0% schema coverage, and an undocumented 'camera' parameter. For a dual-mode read/write tool the description does not explain how to invoke read versus write, making it under-specified 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% for two parameters. The description compensates for 'speed' by giving its range (1-5) and meaning, but 'camera' is entirely undocumented in both the schema and the description, leaving a meaningful gap.

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 pair and resource: read or set the preset switching speed, with the numeric range (1-5) and location ('Center's Console page'). The elaboration 'How fast recalls drive the gimbal' clarifies the effect, distinguishing it from preset_recall/preset_save siblings, though it stops short of naming those siblings directly.

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 'Read or set' implies two modes, but there is no guidance on when to use this versus obsbot_tail2_gimbal_speed or the preset recall tools, and no prerequisite or context is given. An agent must infer usage entirely.

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