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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them by specifying the exact return fields and, notably, that it never returns the password or PIN itself — a meaningful security disclosure an agent would not otherwise know, plus the auth requirement.

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?

Front-loaded and appropriately short, but the first sentence and the second sentence overlap on 'photo count' and 'cover and gallery URL', which is mild redundancy rather than distinct 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?

With no output schema, the description correctly carries the return-value burden and lists the concrete fields, so an agent knows what comes back. It is nearly complete; the only minor gap is noting any error behavior when the collection is not found or access is denied.

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% (collection_id documented as 'Collection ID from list_collections'), so the schema already carries the parameter meaning. The description does not mention collection_id or add any syntax beyond the schema, so the baseline of 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?

States a specific verb ('Get') and resource ('collection'), then enumerates exactly what the single returned collection contains (name, event date, photo count, gallery URL, privacy flags). The singular scope clearly distinguishes it from the sibling pixieset_list_collections.

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 singular 'One collection' framing versus list_collections; there is no explicit when-to-use or when-not guidance. It does add the prerequisite that a Cotlet API key with access to this app is required, which is useful context but not routing guidance.

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