set_blackbox_sample_rate

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

With no annotations, the description carries full burden. It explains the effect on logging rate and size, but the parameter type is ambiguous: the schema expects a string, yet the description says '[UINT8, default: 1/4]', which could confuse an agent about the exact format required. It also does not clarify whether the change is persistent or immediate.

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 concise, with only three sentences. It front-loads the purpose, provides examples, and notes the default and type information. Every sentence is informative and earns its place.

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 tool's simplicity and lack of output schema, the description covers the core aspects: purpose, parameter effect, and examples. It does not explain persistence or immediate effect, but that is common for such settings. The type ambiguity is a minor gap.

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 schema has 100% coverage with a basic description, but the tool description adds significant value by explaining the fraction concept, giving concrete examples with gyro rate, and stating the default. However, the UINT8/string inconsistency slightly detracts from clarity.

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: 'Set blackbox_sample_rate: Fraction of PID loop iterations logged.' It uses a specific verb ('Set') and resource ('blackbox_sample_rate'), and distinguishes from the many other set_* tools by focusing on the sampling rate.

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 description provides implicit usage guidance by explaining the trade-off between log rate and size ('Finer rates = larger logs'), helping the agent understand when to use finer or coarser rates. However, it does not explicitly compare to other blackbox-related settings like mode or device.

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