get_collection_images

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does mention pagination and the limit max (100), which is useful context. However, it does not explicitly state that this is a read-only operation, describe the return format, or address error behavior (e.g., invalid collection_id).

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 exceptionally concise: one clear sentence plus a simple arg list. It front-loads the primary purpose and includes essential parameter details without any wasted words.

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 tool with no output schema or annotations, the description is brief but somewhat adequate: it covers the basic action and parameters. However, it omits the return value structure (what an 'image' object contains), potential error scenarios, and any relation to sibling tools, leaving gaps that an agent must guess.

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 has 0% description coverage, so the description's parameter notes add important meaning: 'limit' is described as 'Max results (default 100, max 100)' and 'offset' as 'Pagination offset'. However, the stated default of 100 conflicts with the schema's default of null, creating ambiguity. The description adds some value but the inconsistency weakens 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 clearly states the tool's action ('Get images') and resource ('in a collection'), with the pagination detail distinguishing it from simple list tools. It is specific and unambiguous, and the name reinforces the purpose.

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 provides no guidance on when to use this tool versus alternatives like search_library or list_collections. It does not mention any exclusions, prerequisites, or related tools, leaving the agent to infer usage purely from the name.

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