bosch_sync

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

No annotations provided, but description fully discloses behavior: fetches data from Bosch, stores in SQLite, sources depend on sign-in, and that some data types are only available with euda client. Also describes return format.

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?

Well-structured with paragraphs and clear sections, though the 'Args' section partly repeats some info. Still concise and front-loaded with 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?

Given the complexity (sign-in types, data sources, availability differences), the description covers all essential context. Output schema exists but description still explains return format.

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?

Only parameter data_types has 0% schema coverage, but description adds full meaning: lists options (all, bikes, batteries, etc.), explains comma-separated, and notes default 'all'.

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 'Sync Bosch eBike data to the local cache,' which clearly states the verb and resource. It distinguishes from sibling tools (bosch_get_*) by explaining it populates the cache they read from.

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?

Explicit guidance: 'Run this to populate the cache before using other bosch_get_* tools, or to refresh after a ride or charge cycle.' Also explains data availability differences based on sign-in type.

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