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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description's help. The description adds which fields are returned, but with an output schema present that is largely redundant, and it says nothing about error behavior for a missing or inaccessible collection.

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 with the resource, the selector, and the returned payload front-loaded. Nothing is redundant and nothing could be cut without losing information.

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 one-parameter read tool with full annotation coverage and an output schema, this is nearly complete: identity, selector, and return contents are all covered. The remaining gap is a brief note on not-found or permission-denied behavior, which matters for an agent recovering from a failed lookup.

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% and the collection_id parameter is documented with its provenance ('from list_articles or an article's collection field'), which is genuinely useful sourcing guidance. The description itself adds no parameter detail beyond 'by ID', which is consistent with the schema but not additive.

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 states a specific verb and resource ('Get a collection by ID') and enumerates the payload ('metadata, article counts, and privacy settings'), so the agent knows exactly what it retrieves. It implicitly contrasts with list_collections via 'by ID' but never names that sibling, so differentiation is inferred rather than stated.

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?

Usage is only implied: the 'by ID' framing signals this is the detail-fetch used once an ID is known, typically after list_collections or from an article's collection field. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of what happens if the ID does not exist.

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