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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses auth requirements (owner's session with origin and CSRF checks), that org API keys stay within existing grants, and that responses use 'private, no-store' caching. That is real context the annotations do not carry. Some of it concerns the sharing model rather than this read operation, so it is not fully on-target.

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 relevant 'what this does / caching' content is front-loaded, but a large share of the text enumerates sharing, revocation, and publishing rules that are tangential to reading a team grant. Several sentences do not directly earn their place for this tool.

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?

With no output schema, an agent gets no picture of what a 'team grant' response actually contains (roles, members, access flags). Auth and caching behavior are covered well, but the return shape is left entirely to inference.

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 single parameter (collection_id) is fully documented as the 64-character resource ID. The description adds no format, sourcing, or discovery hint for that ID, so 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 gives a clear verb+resource: 'Read the team grant for your collection.' That distinguishes it as the read-side counterpart to share_collection_team / unshare_collection_team, though it never names those siblings explicitly. The remaining sentences drift into sharing semantics rather than reinforcing what this tool returns.

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 statement of when to call this tool versus share_collection_team, unshare_collection_team, or team_get_collection. The description explains team-access semantics broadly but never routes the agent to or away from an alternative. Usage must be inferred entirely from the name.

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