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

Annotations already cover the safety profile (readOnlyHint, destructiveHint, openWorldHint), and the description adds substantive context beyond them: it reveals the on-disk location (content/<id>/collection.json) and that read-only status is split between Xodia collections and other content on the plan. 'Reads only' merely restates readOnlyHint, but the payload disclosure is genuinely additive.

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?

It is front-loaded correctly, opening with the verb and resource, but the remainder is one sprawling run-on clause chain with nested parentheticals that is hard to parse. Each enumerated field does carry information (there is no output schema), so little is truly wasted, but the structure could be split into a purpose sentence plus a returns sentence.

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 full burden of describing return values, and it does so in unusual detail: item counts, URLs, fields, non-CMS content, kit presence, plan limits, and read-only flags. The only missing piece for full completeness is routing guidance against sibling tools.

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 both branch semantics (defaults to the open branch) and projectId provenance (from list_projects) documented in the schema. The description adds no further meaning about either parameter, 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?

States a specific verb and resource ('Lists the site's Xodia CMS collections') and enumerates the payload (item counts, item URLs, fields, CMS kit presence, plan limits), so the agent knows exactly what it gets. It never contrasts itself with near siblings like get_collection (single collection) or list_items, so differentiation is left to inference.

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 explicit 'use this when' or exclusion; the closest thing is the aside that some content is 'read another way (folders, data/, Decap)' and a passing reference to 'starters create_collection offers'. An agent must guess whether to call this versus get_collection or list_items when it needs one collection's details.

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