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

While annotations cover safety (readOnlyHint: true), the description provides specific behavioral context by listing the metadata returned (artist, size, release date). This helps the agent anticipate the utility and content of the resulting list.

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 sentence is extremely concise, directly stating the action and the scope of the data provided without any extraneous language.

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 that the tool accepts 0 parameters, the description fully communicates what the tool achieves and the quality/type of data it returns, making it contextually complete for the agent.

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?

Since there are 0 parameters, the baseline is high. The description adds value by defining the fields that will be contained within the collection list (artist, size, release date), which is helpful without an output 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?

The description uses a specific verb ('List') and clearly identifies the resource ('BrainDrops collection'). By listing 'every' collection, it defines its scope and distinguishes itself from specific retrieval functions like get_collection or search_braindrops.

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 defines the tool's function as a complete enumeration of resources. Compared to sibling tools that suggest specific filtering or detail fetching, this tool is clearly identified as the high-level comprehensive list function.

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