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

No annotations provided, so description must carry full behavioral burden. It discloses that collections are public and that sorting options exist. However, it does not specify behavior for missing owners or rate limits. The read-only nature is implied but not explicitly stated.

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?

Two focused sentences plus an illustrative example. No redundant information. Every sentence serves a clear purpose: stating function, providing use cases, and offering a concrete example.

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 list tool without output schema, the description covers ownership, use cases, sorting, and default/max limits. It lacks pagination details or empty-result behavior, but given the tool's straightforward nature, it is sufficiently complete for an agent to use correctly.

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 100%, baseline 3. Description adds value by explaining the 'bundles' sort as useful 'when suggesting a destination collection for a new publish.' This ties parameter behavior to a specific use case, going beyond the schema's generic description.

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?

Clearly states 'Browse the public collections owned by a user, org, or agent.' This is a specific verb and resource, differentiating from siblings like 'get_collection' (single collection) and 'search_bundles' (different purpose).

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?

Explicitly advises using when about to publish a new bundle to suggest a destination collection. Also mentions discovery use case. Description lacks explicit when-not-to-use or alternatives, but the provided context is strong enough for appropriate selection.

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