get_connected_devices

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

With no annotations, the description carries the burden. 'List' clearly implies a read-only operation, but the description does not disclose any additional behavior such as whether only currently paired devices are returned or whether ordering is meaningful. This is adequate but minimal for a simple list call.

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?

One short, front-loaded sentence with no filler. Every word contributes meaning: 'List', 'all', 'connected', and 'Garmin devices'.

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 zero-parameter list tool with an output schema, the description is nearly complete. The only real gap is the exact meaning of 'connected' and how this relates to get_device_info, but that is minor given the trivial call signature.

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 parameter documentation is inherently unnecessary. The description's phrase 'all connected Garmin devices' communicates the implicit scope of the operation.

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 a specific resource ('all connected Garmin devices') and a clear list/retrieve action. The plural 'devices' and qualifier 'connected' help differentiate it from singular or profile-oriented sibling tools like get_device_info.

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?

There is no guidance on when to use this tool versus get_device_info or other sibling tools. It does not mention whether this is a prerequisite for device-specific calls or how 'connected' is scoped.

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