bosch_sync

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

With no annotations, the description fully carries the burden of behavioral disclosure. It explains internal storage (SQLite), API source selection based on sign-in type, automatic bike identification, battery time series behavior, and the 'unavailable' status for non-euda accounts, providing deep insight beyond the raw function.

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?

Despite being detailed, every sentence adds value. The structure is clear: a one-sentence summary, followed by behavior, usage context, caveats, args, and return format. It is front-loaded and avoids redundancy, making it easy for an agent to parse quickly.

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 description covers all critical aspects for a sync tool: purpose, prerequisites, data types, return format, and account-specific limitations. It even explains edge-case behavior (status 'unavailable' vs empty). Given the simple one-parameter schema and no annotations, this is exceptionally complete.

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 offers no description for data_types (0% coverage), but the description compensates comprehensively by listing all valid options, explaining comma-separated multi-selection, providing examples, and stating the default. This fully compensates for the schema gap.

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 opens with a clear, specific verb+resource statement: 'Sync Bosch eBike data to the local cache.' It further distinguishes this from sibling getter tools by positioning it as the prerequisite for bosch_get_* tools, making its role unmistakable.

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?

Explicitly instructs when to run this tool ('before using other bosch_get_* tools, or to refresh after a ride or charge cycle') and provides context about account-type-dependent data availability. This leaves no ambiguity about appropriate invocation timing.

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