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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered; "Reads only" merely restates it. The description does add value by disclosing the payload shape (settings, groups, fields with rules/options, page settings, item count, CMS kit state, route/routing state), which substitutes for the absent output schema. It says nothing about failure behavior for a missing collection or branch fallback semantics.

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 with the verb and resource, then the return contents, then the precondition — a sound ordering. It is a single very long sentence, though every listed item is substantive rather than filler, so the density costs little readability.

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 carries the burden of telling the agent what comes back, and it does so comprehensively across settings, fields, page config, item count, and field-value write semantics. Combined with the precondition guidance, an agent can decide to call it and know what to expect.

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%, with each of the three parameters documented in-schema (projectId from list_projects, collection id from list_collections, branch default). 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?

"Reads one collection" gives a specific verb and singular resource, immediately distinguishing it from the plural sibling list_collections and from update_collection/create_collection. The sentence then enumerates exactly what a collection read yields, so an agent knows what it gets without opening a schema.

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?

It supplies a concrete precondition: "Read it before writing items or binding a page," which tells the agent where this sits in a workflow. It does not name a sibling alternative or an explicit when-not-to-use case (e.g. use list_collections to discover ids), though the schema parameter text does point at list_collections.

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