bosch_get_bikes

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

No annotations are provided, so the description discloses useful behavioral traits: it uses a local cache with auto-sync, and advises running bosch_sync if the list is empty. This goes beyond the empty schema and adds meaningful context about data freshness.

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 concise and front-loaded with the purpose in the first line. It provides only essential extra guidance (cache and sync) without fluff, and every sentence serves a purpose.

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 covers the main purpose, return contents, and cache behavior. It also includes a helpful tip about syncing, making it complete for the tool's simplicity.

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 schema coverage is effectively 100%. The description doesn't need to add parameter details, and the baseline for 0 parameters is 4.

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 starts with 'List all Bosch eBikes registered to your Flow account', which is a specific verb (List) and resource (all Bosch eBikes) with a clear scope. This clearly distinguishes it from the singular bosch_get_bike sibling.

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 provides a concrete prerequisite by saying 'Run bosch_sync first if the list is empty', which tells the user when to perform a sync before calling. It doesn't explicitly exclude alternatives, but the 'all' vs singular naming makes the usage context clear.

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