collection_summary

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds valuable behavioral context by stating the data comes 'from the cache' and that a last sync time is returned, which tells the agent the result may be stale. It stops short of detailing cache refresh semantics or permissions.

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 single, front-loaded sentence that efficiently enumerates the returned aggregates. Every item earns its place by clarifying the tool's scope and output content.

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?

There is no output schema, so the description appropriately enumerates the returned counts and metadata. However, for a tool with one parameter, omitting any explanation of the 'top' parameter leaves a notable invocation gap. The definition is adequate but incomplete for correct parameter use.

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 input schema has one parameter, 'top', with 0% description coverage and a default of 15. The description never mentions this parameter or what it controls, so the agent cannot know how to invoke it meaningfully beyond accepting the default.

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 specific verb-resource pair ('Collection overview') and enumerates the exact aggregates it returns: counts by genre, style, label, artist, decade, format, country, duplicate masters, and last sync time. This makes it clearly distinguishable from siblings like query_collection, get_collection_value, and export_collection.

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 a summary use case by listing aggregate outputs, but it never says when to choose this tool over alternatives such as query_collection or get_collection_value, nor does it mention exclusions or prerequisites. No explicit usage guidance is provided.

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