collection_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool lists collections, with no mention of read-only semantics, authentication requirements, pagination, ordering, or the meaning of 'native'. This is a significant gap for a tool with zero annotation support.

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?

The description is a single, concise sentence with no wasted words. It is slightly under-specified, particularly the ambiguous 'native' qualifier, but it remains appropriately brief for a no-parameter tool.

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?

Given the tool is simple (no parameters, output schema exists), the description is mostly adequate, but the undefined term 'native' and lack of behavioral details such as pagination or ordering leave room for agent confusion. A sentence clarifying 'native' or noting the output shape would make it complete.

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?

The tool has zero parameters and the schema is already fully described (100% coverage), so the baseline of 4 applies. The description correctly adds no parameter information because there are no parameters to document.

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 states a specific verb ('List') and resource ('all native collections'), making the tool's purpose immediately clear. Among siblings, there is no other collection-list tool, so the name and description together distinguish it from collection_create, collection_edit, collection_delete, and collection_set_emoji.

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?

No guidance is given about when to use this tool versus alternatives, nor any exclusion criteria. The qualifier 'native' vaguely implies a distinction from non-native collections, but this is not explained, leaving the agent to infer usage context.

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