Refresh the local index

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

No annotations, but description discloses behavior well: full library pull (~20s), incremental listens, and cache semantics. It doesn't state side effects like network dependency or potential cache invalidation, but is reasonably transparent for a cache refresh.

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 focused sentences: action, behavior, when-to-use. No wasted words; front-loads the verb.

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?

Covers purpose, timing, and usage trigger. Missing explicit mapping of 'and/or' sources to scope, but output schema is absent and the tool is simple, so it's largely 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?

Schema covers 100% of parameters with descriptions. Description adds context about the pull behavior (full vs incremental) that maps to scope/full_listens, but doesn't explicitly link parameters to behavior, so marginal value beyond 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?

Uses specific verb 're-sync' and identifies resources (Navidrome, ListenBrainz). Clearly distinguishes from sibling tools that manage playlists or query data; this tool maintains a local cache.

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?

Provides explicit condition: 'Call this if the library changed and results look stale.' While alternatives aren't named, it clearly places this tool as the refresh mechanism for all read-oriented siblings.

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