set_horizon_limit_degrees

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that the tool sets a parameter, but does not disclose side effects, persistence, or whether changes take effect immediately. The agent is left guessing about the impact.

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 a single sentence that efficiently conveys the tool's purpose, the parameter's role, and its constraints. No redundant or extraneous information is present.

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 simple setter with one parameter and no output schema, the description is largely complete. It explains the parameter's function and valid range. However, it lacks information about post-set behavior or any required system state (e.g., connection status), which would enhance completeness.

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 already defines the parameter with 100% coverage, but the description adds significant semantic value by explaining the parameter's purpose ('maximum attitude angle before horizon mode enforces leveling') and providing range constraints ([UINT8, 10–250, default: 135]). This goes beyond the schema's generic 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?

The description clearly states it sets the 'horizon_limit_degrees' parameter, which is the maximum attitude angle before horizon mode enforces leveling. It distinguishes this from sibling getter tools (e.g., get_horizon_limit_degrees) and other setter tools by specifying the exact resource and its role.

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 no guidance on when to use this tool versus alternatives. It does not mention that to read the current value one should use get_horizon_limit_degrees, nor does it explain any prerequisites or context for setting this parameter.

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