vibo_export_event_to_spotify

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

Discloses write operation (export), confirmation requirement, and return values (playlist URL, counts). No annotation contradictions; readOnlyHint=false aligns with mutation. Could mention whether existing playlists are overwritten.

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 sentences, each serving a purpose: action+prerequisite, output, and confirmation gate. No redundant words.

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 core functionality, prerequisites, confirmation, and output. Does not elaborate on the preview behavior when confirm is false, but overall sufficient for a tool with no output schema.

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 coverage is 100%, but description adds defaults ('defaults to the event title'), behavior hints ('Must be true to proceed. Without this, the tool returns a preview'), and usage guidance ('from vibo_list_sections', 'rarely needed'). This goes beyond the 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?

Description specifies 'Export an event's song selections to a new Spotify playlist', a clear verb+resource action. The distinct platform (Spotify) differentiates it from the sibling tool vibo_export_event_to_apple_music.

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?

Mentions prerequisite 'Spotify must be connected' and 'Confirm-gated', but does not explicitly state when to use this over alternatives (e.g., Apple Music) or provide exclusions. Usage context is implied by the name and sibling presence.

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