get_telemetry

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

Without annotations, the description carries full burden. It discloses 'Read-only' behavior and that fields not reported within a few seconds are null. It does not cover connectivity scenarios or refresh semantics, but the null-handling is a valuable behavioral trait.

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 three sentences with no wasted words. It front-loads the purpose and key traits, then efficiently provides return structure, null handling, and a usage advisory.

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 no parameters and an existing output schema, the description is complete. It covers the tool's purpose, behavior (null fields), and use-case advisory. No obvious gaps remain for a simple telemetry read.

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?

There are zero parameters and schema coverage is 100%. The description adds value beyond the schema by explicitly listing the returned fields (position, attitude, battery, gps, flight_mode, armed, in_air) with their subfields, which aids an agent in understanding what to expect.

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 'Read one snapshot of the vehicle's telemetry. Read-only.' It uses a specific verb ('Read') and resource ('telemetry snapshot'), and the purpose is distinct from siblings like `get_flight_mode` or `get_capabilities`.

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 implicitly advises when to use the tool with 'Always check telemetry before commanding motion,' and declares it read-only (safe, no side effects). It does not explicitly state when not to use it or list alternatives, but the sibling context provides differentiation.

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