Get Collection

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does explain the conditional effect of include_market_data and that lookup can be by id or name, but it does not mention not-found behavior, authentication requirements, or any other operational side effects.

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?

A single sentence packs the core purpose, lookup modes, returned content, and parameter-driven behavior. It is front-loaded and contains no filler.

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 low complexity, the presence of an output schema, and clear parameter semantics, the description is nearly complete. The only minor gap is explicit guidance on when to use this tool versus listing collections, but that is not essential for a standard get-by-identifier operation.

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 0%, but the description compensates by explaining both parameters: collection can be a hex id or a name, and include_market_data controls whether floor price, volume, and holder metrics are returned. This fully covers what the bare schema lacks.

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 fetches one collection, identified by hex id or name, and returns its stamps plus optionally market data. This distinguishes it from list_collections and get_stamp by specifying the resource and retrieval mode.

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: call this when you need a specific collection's details by id or name. However, it does not explicitly say when to prefer list_collections or other siblings, nor does it provide exclusions or alternative conditions.

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