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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds real substance: team access is evaluated per request against membership/product access/sharing, revocation blocks search and downloads even with a live session or key, the initial grant needs owner session with origin and CSRF checks, org API keys stay within existing grants, and responses are private/no-store. This goes well beyond the annotations, though much of it is sharing-policy detail only loosely tied to a read 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?

Seven dense sentences of access-control prose, most of it about sharing grants and revocation rather than reading a collection. The single sentence that states purpose is buried under tangential policy text, so the definition is neither front-loaded nor free of filler for the task at hand.

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?

There is no output schema, so the description should describe what a 'get collection' returns, but it never mentions the collection's fields or payload shape — only that responses are private/no-store. Behavioral and auth context is unusually thorough, but the return-value gap leaves the definition only adequately 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 coverage is 100% and both required parameters (collection_id, organization_id) are fully documented in the schema, including the membership/OKFIndex precondition. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 opening sentence 'Read your collection and accessible base references' names a verb and resource, but 'accessible base references' is vague and never clarified. With siblings like get_collection, public_get_collection, team_list_collections and team_get_base, the description never distinguishes when this team-scoped variant is the right call. Purpose is inferable but not sharp.

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 never states when to use this tool versus the many sibling collection tools (get_collection, public_get_collection, team_list_collections). It discusses access policy at length but gives no selection criteria, prerequisites, or exclusions for invocation.

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