get_connection_status

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

No annotations are provided, so the description carries full burden. It discloses the critical lazy-connection behavior ('connected is false until another tool has been used') which is essential for correct interpretation of the result. This exceeds expectations.

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?

Three concise sentences front-loading purpose, then providing essential behavioral context and usage guidance. Every sentence is necessary and earns its place. No 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?

The tool has zero parameters and an output schema. Given this simplicity, the description is fully complete: it explains what is reported, the lazy-connection nuance, and the diagnostic usage pattern. No gaps remain.

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?

Schema description coverage is 100% with zero parameters, so baseline is 3. The description adds value by stating 'Takes no arguments' upfront, confirming no hidden inputs. A 4 is appropriate for a param-free tool where the description reinforces the schema.

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 reports the MAVLink endpoint, connection state, and guardrail config. It is a singular, specific verb+resource combination that is easily distinguished from sibling tools like arm, takeoff, or get_telemetry.

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 explicitly tells the agent to check this first when other tools report errors, and explains the lazy-connection behavior that makes this diagnostic. It provides clear context for when to use this tool versus alternatives.

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