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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description only needs to add context. It does add one useful fact — that the response includes the actual members of each collection, not just collection metadata, and that both core and specialized collections are included. It says nothing about pagination, ordering, or response size, which are relevant for a listing call with no output schema.

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 sentence with no filler, and the resource being listed is front-loaded. It is efficient, though its brevity is partly the reason important details are missing.

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 listing tool with no output schema and an undocumented 'query' parameter, the description should explain what a collection record contains, how 'query' narrows results, and whether results are paginated. It only hints that members are included, leaving key calling details unknown.

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 50%: only 'version' is documented in the schema, while 'query' has no description anywhere. The description never mentions either parameter, so it adds no meaning about what 'query' filters on (collection name? member?) or how 'version' changes the result set. With half the parameters undocumented, the description fails to compensate.

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?

The description names a specific verb and resource ('Lista as coleções do catálogo') and adds meaningful scope: it covers both core and specialized collections and returns the real members of each. That is more than a restatement of the title. It does not explicitly contrast itself with siblings like refy_search or refy_component, so it stops short of a 5.

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 statement of when to use this tool rather than refy_search or refy_component, and no prerequisites or exclusions. At best the phrase about 'membros reais' hints that it is for discovering collection membership, but the agent must infer that usage entirely.

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