get_s_roll

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

No annotations are provided, so the description carries the burden. It mentions the data type (UINT8, default 0) and that it's new, but does not explicitly state read-only behavior or what happens if USE_WING is not enabled (likely error or default returned).

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: one sentence plus metadata. Key information is front-loaded with no extraneous content.

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 parameterless getter with no output schema, the description covers purpose, requirement, and return type. It could be improved by explaining 'additional stability control' or potential error cases, but overall is fairly 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?

There are no parameters (schema coverage 100% empty), so the description adds value by specifying the return type 'UINT8, default: 0', helping the agent understand the output format.

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?

Description clearly states 'Get s_roll: S-term (stability term) for roll.' The verb 'Get' and resource 's_roll' are specific, and mentioning 'roll' distinguishes it from siblings like get_s_pitch and get_s_yaw.

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 requirement 'Requires: USE_WING' provides clear context for when this tool is applicable. For a simple parameterless getter, this is sufficient guidance; no explicit alternatives are needed as the purpose is straightforward.

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