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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the description need not repeat those. It adds useful context that coverage 'grows as new fandoms are added' and notes filtering behavior, but it does not disclose return format or pagination, which are absent from annotations and output schema.

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 bit long but organized: purpose, when-to-use, coverage examples, and filters. The first sentence is slightly awkward ('besot indexes') and the coverage examples add length, but each section earns its place by helping an agent decide when to call the tool.

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?

For a read-only browse tool with two optional filters and no output schema, the description provides purpose, usage timing, coverage, and parameter behavior in natural language. It does not describe the shape of returned collection objects, but that is a minor gap given the simple list semantics.

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 only 50% because artist has no description. The description compensates by explaining both filters: 'Filter by artist, or by type: collaboration, capsule, or artist-founded brand,' and the examples make the artist filter concrete with names like Harry Styles and Beyonce. This adds meaning beyond the schema's minimal type description.

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 specific verb and resource: 'List the collections besot indexes' and immediately defines the resource as collaborations, capsule drops, and artist-founded brands. It differentiates from siblings by framing this as the coverage/browse tool while search_pieces is implied as the search path.

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?

It gives explicit when-to-use guidance: 'Use this when someone asks what a given artist has made, which artists have worked with a given brand, or what is covered before running a search' with concrete examples. It does not explicitly name sibling tools as alternatives or state when not to use it, so it lacks the full when-not/alternatives specificity.

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