get_tpa_speed_pitch_offset

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not explicitly state that the tool is read-only or safe, though that is implied by the 'get' prefix. The description adds minimal behavioral information beyond the name and prerequisite.

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 and well-structured: a short title-colon-purpose, a prerequisite in parentheses, and type/default. Every sentence adds value and there is no fluff.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description covers the essential aspects: purpose, prerequisite, and output type. It is almost complete, though it could be slightly improved by explicitly stating the tool returns the current value or that it is a read operation.

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, so the description has no parameters to document. However, it provides valuable information about the return value: datatype INT16 and default 0. This goes beyond what the empty input schema offers and helps the agent understand the output.

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 the tool's purpose as returning the pitch offset correction for speed TPA for wing/fixed-wing trim. It adds context beyond the tool name, such as the requirement for USE_WING, which helps differentiate it from other parameters. However, it does not explicitly state 'get' or 'retrieve', relying on the tool name, but the colon-separated format makes the purpose clear.

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 only usage guidance is the prerequisite 'Requires: USE_WING', which is useful but does not provide any when-to-use or when-not-to-use instructions. There is no mention of alternatives or exclusions, which is a significant gap given the large number of sibling tools.

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