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

No annotations exist, so the description carries the behavioral burden, but the tool is a search/list operation and the description adds the key behavioral nuance that an omitted query returns all collections. It does not explicitly disclose read-only status, auth needs, or pagination behavior, leaving some behavior implicit for a tool with no annotation safety net.

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?

Single compact sentence with high-value details: community scope, examples, ID format, and list-all behavior. No filler and the most important information appears first.

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 an output schema present and only one required parameter, the description gives enough to call the tool correctly: the required community identifier format and the optional query behavior are specified. Limit/pagination details and any access constraints are not elaborated, but the schema defaults and output schema cover much of the remaining need.

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%, but the description compensates by explaining that community_id accepts a UUID or slug and that query is optional, with omission meaning 'list all collections'. Limit remains only schema-defaulted with no additional semantics, so the compensation is strong but not complete.

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 the exact operation ('Search for collections') and the scope ('within a Compoid community'), with concrete examples and a list-all mode. This clearly distinguishes it from sibling search_communities/search_records even though they aren't named.

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?

Gives clear context: collections belong to a community, and omitting query lists all collections, which tells the agent when a broad listing is appropriate. It does not explicitly contrast with search_records/search_communities or state exclusions, but the target resource is unambiguous.

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