get_collection_contents

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says 'Get', which weakly implies a read operation, but it does not mention pagination behavior, response structure, filtering effects, or any side effects. This leaves the agent with limited understanding of how the tool behaves beyond the basic operation.

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, efficient sentence with no redundant wording. It front-loads the core purpose and adds the clarifying parenthetical in a compact way.

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 simple read-only listing tool, the schema provides most required parameter context, and the description identifies the response categories. However, with no output schema and no annotations, the description omits useful details such as pagination defaults and what fields are returned for each asset or sub-collection. It is adequate but not fully 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?

Schema description coverage is 50%, with collection_id and content_types described in the schema. The description adds meaning by explaining that contents are 'assets and sub-collections', which aligns with the content_types enum values, but it does not clarify pagination defaults or the meaning of page/per_page beyond what the schema already shows.

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 operation: 'Get the contents (assets and sub-collections) of a collection.' It names the specific resource and scope, and the parenthetical distinguishes it from sibling tools like get_collection_subcollections, which only handles sub-collections. An agent can readily understand what this tool does.

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 the tool is used when you need both assets and sub-collections within a collection, but it does not explicitly state when to prefer it over list_assets, get_collection_subcollections, or get_collection. No exclusion criteria or alternative routing is provided.

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