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

Goes well past the readOnly/idempotent annotations by disclosing caching semantics ('Responses use private, no-store'), failure behavior ('Private or withdrawn collections return 404'), that collections hold references rather than copied content, and that every public read re-checks base publication. These are exactly the behavioral traits annotations cannot express.

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 lead sentence is well front-loaded, but the middle sentences drift into general collection/publication model lore ('Publication includes only references to currently public bases...') that is only loosely tied to invoking this tool. Dense and partly tangential for a single-parameter read.

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 read-only, single-param tool with full schema coverage and no output schema, the description covers error cases, caching, and content semantics. It could still say more about the shape of the returned collection/reference data, but nothing critical for correct invocation is missing.

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 coverage is 100% and the single parameter already carries its own description, so the schema does the heavy lifting. The description adds no format, length, or lookup semantics beyond it, making the baseline 3 appropriate.

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 first sentence gives a specific verb and resource ('Read your collection and accessible base references'), and 'your' implies the owner-scoped view. However, it never distinguishes itself from the strong sibling set (team_get_collection, public_get_collection, list_collections), so an agent must infer the boundary from context.

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 by the phrase 'your collection' and the owner-search sentence; there is no explicit 'use this when / use X instead' guidance. With three near-identical siblings (team_, public_, list_collections) available, this is a notable gap.

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