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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the behavioral nuance that the `count` field is more trustworthy than PATCH echoes, which is useful. It doesn't disclose any other behaviors like pagination or return format, but since annotations cover the main safety aspects, a 3 is appropriate.

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 concise—one sentence plus an imperative clause. It front-loads the key point ('authoritative contents') and immediately follows with the most important caveat. Every word earns its place, and there is no fluff.

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?

Given that the tool is a simple read operation with one parameter, and the annotations cover idempotency and read-only nature, the description is nearly complete. It adds the crucial caveat about PATCH responses, which is the only non-obvious context an agent needs. The only minor omission is that it doesn't explain what 'contents' means exactly (e.g., links, metadata), but the tool name and title suggest it.

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 there is only one required parameter, `uuid`. The description does not mention `uuid` at all, but with a single parameter named 'uuid' and no enums, the semantics are fairly self-explanatory from the schema. However, the description could have added context like 'the collection's uuid' or format expectations, so the baseline 3 is justified.

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 clearly states the tool retrieves the authoritative contents of a collection, which is a specific resource and action. It distinguishes itself from siblings like split_list_collections and split_get_collection_embed by emphasizing 'authoritative contents' and the explicit caveat about PATCH responses, which subtly differentiates it. However, it doesn't explicitly name an alternative sibling that provides similar but different data, so it's not a 5.

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 advises using the `count` field to verify membership and warns against trusting PATCH-response link counts. This provides clear context on when to use this tool (for reliable membership checks) and implicitly when not to (when you have a PATCH response). It doesn't explicitly name alternative tools for getting collection info, but the guidance is actionable and context-rich.

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