collection_items_top

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

No annotations provided, so description bears full burden. Only states the retrieval action without disclosing that it is read-only, returns only top-level items (not subitems), or any pagination or auth requirements. Minimal transparency.

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 concise sentence with no redundant information. Front-loaded with key action and resource. Every word adds value.

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?

Together with a detailed input schema and an output schema (present but not shown), the description covers the basic purpose. However, it omits behavioral details like read-only nature and scope (top-level only). Almost complete given the tool's simplicity.

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 descriptions for parameters are comprehensive (e.g., q, qmode, collection_key), so baseline is 3. The tool description does not add any parameter-level meaning beyond the schema, but does not need to given schema richness.

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?

Description clearly states 'retrieve top-level items in a collection', specifying verb and resource. Distinguishes from sibling tools like 'collection_items' (likely retrieves all items) and 'top_items' (top-level across collections, not scoped). However, the description could explicitly differentiate use cases.

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 on when to use this tool vs alternatives like 'collection_items' or 'top_items'. Does not state that it only returns direct children of the collection or mention prerequisites (e.g., requiring a collection key).

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