set_gps_sbas_mode

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

With no annotations, the description carries the full burden of behavioral disclosure. It only reveals that the tool sets the SBAS mode and mentions the data type and default, but does not disclose side effects, prerequisites (e.g., GPS connection), or behavior for invalid values.

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 succinct sentence that effectively conveys the purpose and includes key type and default information. No wasted words.

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?

The tool is simple with one parameter, but the description lacks explanation of valid values, region-specific behavior, or output. Without annotations or output schema, the description should provide more context for a complete understanding.

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 baseline is 3. The description adds that the value is a UINT8 with a default of 'NONE', which is not explicit in the schema (schema says string, no default). This adds marginal value beyond the schema.

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 verb 'Set' and the resource 'gps_sbas_mode' which is the SBAS (satellite correction) system for the region. It distinguishes from the getter sibling `get_gps_sbas_mode` but does not explicitly differentiate from other GPS set tools like `set_gps_sbas_integrity`.

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?

No guidance is provided on when to use this tool versus alternatives such as `set_gps_sbas_integrity` or other GPS configuration tools. The description lacks context about prerequisites or scenarios for setting SBAS mode.

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