get_spa_pitch_mode

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

No annotations are provided, so the description carries the full burden. It discloses the requirement of USE_WING and the default value, which are helpful. However, it does not mention any other behavioral traits such as safety or side effects; since it is a getter, the implied read-only nature is acceptable but not explicit.

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 very concise with three key pieces of information: purpose, requirement, and type/default. It is front-loaded and contains no extraneous text.

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 main aspects: what it retrieves, a prerequisite, and default value. It does not explain what the mode values represent or enumerate possible values, but for a basic configuration read, it is reasonably 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?

The tool has zero parameters in the schema. The description adds value by specifying the type (UINT8) and default value (OFF per profile), which are not in the schema. This is sufficient for a parameterless getter.

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 indicates it's a getter for 'spa_pitch_mode' and specifies it relates to pitch. Among siblings like get_spa_roll_mode and get_spa_yaw_mode, it is distinct. However, the meaning of 'SPA mode' is not explained, which slightly reduces clarity.

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 includes a requirement 'Requires: USE_WING', which provides context for when this tool is relevant. However, there is no explicit guidance on when to use this versus alternatives (e.g., get_spa_pitch_center) or when not to use it.

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