set_acc_limit_yaw

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

Discloses that 0 means 'no limit', and provides value range and default. However, does not mention persistence or side effects like requiring reboot or immediate effect. With no annotations, more behavioral detail would be helpful.

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?

Extremely concise: two short sentences with no redundant words. Purpose, sibling reference, special value, and format are all front-loaded.

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?

Adequately describes a simple setter with one parameter. Covers purpose, range, default, and special value. Could mention effect timing, but given the tool's simplicity and lack of output schema, it is reasonably complete.

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 has 100% coverage but description adds '0 = no limit' and default value, which are not in schema. Provides meaningful extra context beyond the schema's brief description.

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?

Clearly states the verb 'Set' and resource 'acc_limit_yaw'. References the sibling tool 'acc_limit' to distinguish the yaw axis variant. Provides value range and default. No ambiguity.

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?

Explicitly compares to 'acc_limit', indicating when to use this tool (yaw axis) vs its sibling. However, it does not mention any alternative tools or provide 'when-not-to-use' guidance.

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