get_collection

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

Annotations already provide readOnlyHint=true, and the description adds no extra behavioral context. It does not mention what happens if the collection is not found, whether it returns related items, or any rate limits.

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 extremely brief—almost a tautology of the tool name. It is under-specified and omits useful context that could be conveyed in a short sentence without losing conciseness.

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?

The tool is simple, has a readOnlyHint annotation, and has an output schema (which covers return values). However, the lack of usage guidance and parameter clarification leaves the description incomplete for an agent deciding between this and sibling collection tools.

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%, and the description does not explain the collection_id parameter or how to find valid IDs. The parameter name is self-explanatory, but the description fails to compensate for the lack of schema descriptions.

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 'Get collection details' clearly indicates a read operation for a collection, but it is generic and does not explicitly distinguish itself from siblings like get_collection_series or list_collections. It adds little beyond the tool name 'get_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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites (e.g., obtaining collection_id from list_collections) or exclusions (e.g., not for fetching series within a collection).

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