get_tpa_speed_adv_prop_pitch

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

Without annotations, the description provides behavioral context: it mentions a prerequisite (USE_WING), data type (UINT16), and default value (370). This adds value beyond the schema, though it could detail side effects or return format.

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 a single sentence with supplementary info in parentheses, conveying all necessary information without redundancy.

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 params, no output schema), the description covers the purpose, units, prerequisite, type, and default, making it fully informative for an 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 no parameters, so the description adds meaning by clarifying the value type and default. This compensates for the lack of schema details.

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 states the tool retrieves propeller pitch for the advanced speed TPA physics model, including units (mm) and a prerequisite (USE_WING). It clearly distinguishes itself from other get_* tools by specifying the exact parameter.

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?

While it notes a required feature (USE_WING), it does not explicitly guide when to use this tool versus other tpa_speed_* getters or how it fits into the broader workflow. No alternative tools are mentioned.

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