get_collection

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Service call' and 'a page of its icons' convey that a single call returns a page of icons rather than one icon, and the preference note hints at batching efficiency. However, it does not describe response structure, error behavior, rate limits, or whether the operation is safe and idempotent.

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 opening sentence is front-loaded and specific, and the preference note is useful and compact. The standalone sentence 'Service call' is terse and adds only marginal information, preventing a perfect score.

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?

With six parameters and no output schema, the description gives a high-level result shape but no concrete response format or pagination continuation details. The schema covers parameter meanings, and the description adds batching guidance, so an agent can select and start using the tool, though the definition is not fully self-contained for advanced pagination workflows.

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 description coverage is 100%, so the schema already documents every parameter. The description adds context for the pagination parameters by saying it returns 'a page of its icons,' but it does not explain parameter defaults, token relationships, or enum semantics beyond what the schema provides.

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 the specific verb-object pair 'Get a collection and a page of its icons,' clearly identifying the resource and the paginated nature of the result. The final sentence distinguishes it from get_icon by noting it should be preferred over per-icon calls, making its purpose unambiguous.

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 explicitly instructs the agent to prefer this tool over calling get_icon on each icon, giving concrete selection guidance and naming the relevant alternative. It does not enumerate when to fall back to get_icon or when search_collections would be more appropriate, so the guidance is strong but not exhaustive.

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