get_s_pitch

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

No annotations provided. The description hints at a read-only operation ('Get') and specifies the type UINT8 and default value, but doesn't elaborate on side effects, latency, or other behaviors. Adequate for a simple 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 (one line) and front-loaded with the action and resource. Though it lacks separate lines for requirement and type, it is efficient with zero waste.

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 parameter getter with no input parameters and no output schema, the description covers the essential: purpose, requirement, and value type. However, it does not mention the output format (e.g., a single numeric value), which could be helpful.

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 no parameters, so schema coverage is 100% vacuously. The description adds value by stating the type (UINT8) and default (0), which the schema does not convey.

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 retrieves the S-term for pitch, distinguishing it from sibling tools like get_s_roll and get_s_yaw. The verb 'Get' and resource 's_pitch' are specific.

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 only mentions the requirement 'USE_WING' but provides no guidance on when to use this tool versus alternatives like get_pitch_rate or get_pitch_rc_rate. No explicit context for selection.

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