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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful detail of what the returned definition contains, but says nothing about auth requirements, error behavior for a missing slug, or scoping by site.

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?

A single front-loaded sentence with no filler; the parenthetical lists the payload contents compactly and every clause earns its place.

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?

For a simple read tool with no output schema and annotations covering safety, the description adequately conveys what is returned. However, the undocumented optional site_id parameter leaves a real gap in how the caller should scope the lookup.

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 only 50%: slug is documented in the schema, but site_id is undocumented in both the schema and the description. The description does not compensate for the coverage gap or clarify how a collection is scoped when site_id is omitted.

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 (read) and resource (one collection's definition) and enumerates what the definition contains (schema fields, source, isPublic). An agent can distinguish it from list_collections and update_collection_schema, though it does not name a sibling explicitly.

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 word 'one' weakly implies single-item retrieval, but there is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives like list_collections for enumerating collections. The agent must infer the context.

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