get_user_collection_items

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

With no annotations provided, the description must disclose behavioral traits. It does not mention that the operation is read-only, requires authentication, or how pagination and sorting work. The schema implies some behaviors (e.g., folder_id is required), but the description omits these details.

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, but it is too minimal and lacks structure. Important details like the role of folder_id and pagination are omitted, making it less helpful despite its brevity.

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 6 parameters (2 enums) and no output schema, the description is insufficient. It does not explain that the tool returns items from a specific folder, supports pagination and sorting, or describe the return format. Sibling tools are related, but the description alone is not comprehensive.

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%, so the description should add meaning. It does not explain parameters like username, folder_id, page, per_page, sort, or sort_order. The enums for sort and sort_order are self-explanatory from the schema, but the description contributes no additional semantic value.

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 clearly states the tool retrieves a list of items from a user's collection, using a specific verb and resource. However, it does not differentiate from sibling tools like 'find_release_in_user_collection', which focuses on searching for a single release.

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 versus alternatives such as 'find_release_in_user_collection' or 'get_user_collection_folder'. The description lacks context about typical scenarios or prerequisites.

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