get_yaw_srate

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

No annotations provided. The description does not explicitly state that the tool is read-only or non-destructive. While 'get' implies read-only, the description should confirm no side effects. With zero annotation coverage, the description carries full burden but only mentions type/default.

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 extremely concise—one line with essential info (name, brief definition, type, default). Every part is informative. Could be slightly more structured but is not wasteful.

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 getter with no parameters and no output schema, the description covers the purpose and value details. However, it lacks units for the yaw super rate (e.g., degrees/sec) and does not describe what the value controls or its range. This leaves some ambiguity for the agent.

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 input schema has zero parameters (100% coverage). The description provides inline parameter semantics by stating the return type (UINT8) and default value (67), which adds value beyond the empty schema. This compensates for the lack of explicit parameter documentation.

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 yaw_srate: Yaw super rate.' It identifies the specific resource (yaw super rate) and verb (get). The phrase '[UINT8, default: 67]' adds value by specifying type and default. While it doesn't explicitly differentiate from siblings like get_pitch_srate, the name and description make the yaw focus unambiguous.

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 on when to use this tool versus alternatives (e.g., get_roll_srate, get_pitch_srate). No context about prerequisites or typical use cases. The description is purely declarative with no usage direction.

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