Browse Bandcamp by tag

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds substantial behavioral detail: page size, result shape, pagination contract, label-vs-artist distinction, and a security warning about untrusted user-written text. This far exceeds what the annotations provide.

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 a compact paragraph with every sentence earning its place; core behavior and pagination are front-loaded, followed by edge cases and security guidance. No filler or redundant restatement of the tool name.

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?

Despite having no output schema, the description fully documents the return shape, pagination state, next-page protocol, and a lookup caveat. Given the tool's moderate complexity, nothing needed to invoke or page through the tool correctly is missing.

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 67%, and the description fills the gap: it defines tag slug format with examples, clarifies that omitting tag yields an unfiltered listing, and ties cursor to a prior call with the same tag and sort. It adds meaning beyond the schema rather than repeating it.

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 names a specific action (browse) and resource (Bandcamp releases by genre tag), and further explains the top/new sort and the unfiltered mode when tag is omitted. This distinguishes it from search/get siblings even without naming them.

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 gives clear pagination instructions (same tag and sort plus cursor) and tells the agent to pass a slug to bandcamp_get_album, which routes to a sibling. It also explains the unfiltered tag omission and the null slug limitation, but it does not explicitly state when to choose bandcamp_browse_tag over bandcamp_search.

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