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

With no annotations, the description carries the full burden for behavioral disclosure. The verb 'browse' implies a read-only operation, and it adds context about collection contents ('unique curatorial essence, profile, and recommended viewing context'). However, it doesn't explicitly state that no modifications occur, nor does it clarify the return format or pagination behavior. This is moderate transparency, earning a 3.

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 two sentences, highly concise, and front-loaded with the key action ('Browse all 13 collections and singles'). Every word adds value, and there is no redundant or vague phrasing.

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 the tool's low complexity (one optional parameter, no output schema, no annotations), the description provides sufficient context: it states the scope (13 collections and singles) and hints at the kind of information available. It doesn't explain every edge case, but for a simple listing/browsing tool, this is adequately 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?

The schema already fully documents the single optional parameter 'collection' with a clear description. The tool description adds minimal extra meaning (e.g., mentioning curatorial essence), but this is not necessary for understanding the parameter. With 100% schema coverage, the baseline is 3, and the description doesn't significantly enhance 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 states a clear purpose: 'Browse all 13 collections and singles in César Yagüe's catalog.' It uses a specific verb ('browse') and resource (collections/singles), making its function understandable. However, it does not explicitly differentiate from sibling tools like search_artworks or catalog_overview, so it earns a 4 rather than a 5.

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 implies usage—browsing collections—but provides no explicit guidance on when to choose this tool over alternatives. For instance, it doesn't say 'use this to get an overview of all collections' or 'for specific artwork details, use get_artwork.' This is clear context without exclusions, aligning with an implied usage score of 3.

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