get_spa_roll_mode

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

Without annotations, the description explains the value meanings and the dependency on USE_WING. It also provides the default value and type. This adds meaningful behavioral context for a read-only getter.

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 and front-loaded with the core purpose. Each part (purpose, value explanations, prerequisite, type/default) earns its place without redundancy.

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 parameterless getter, the description fully covers the tool's purpose, meaning of return values, and a prerequisite. No missing information that would hinder correct use.

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 tool has no parameters, so schema coverage is 100%. The description adds value by explaining the possible mode values and their meanings, which is helpful beyond the empty 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 'Get spa_roll_mode: SPA mode for roll', explaining the purpose and the meaning of each possible value (I, PID, PDI_FREEZE). It distinguishes this tool from sibling tools like set_spa_roll_mode and other getters.

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 specifies a prerequisite ('Requires: USE_WING'), giving clear guidance on when this tool is applicable. However, it does not explicitly mention when not to use it or alternatives.

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