get_user_collection_folders

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

The description provides no behavioral details beyond the basic retrieval. No annotations exist, and the description does not mention read-only behavior, permissions, rate limits, pagination, or output format, leaving the agent uninformed about important traits.

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 concise (one sentence, 9 words) but sacrifices necessary detail. It is front-loaded with the purpose but omits essential information about parameters and behavior, making it insufficiently informative for an AI agent.

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 lack of output schema, low parameter coverage, and absence of annotations, the description is critically incomplete. It fails to convey what the agent should expect as output, error handling, or any contextual constraints, leaving significant gaps.

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 single parameter 'username' has no schema description (0% coverage) and the description does not clarify its format, constraints, or requirements beyond 'minLength: 1'. The agent receives no additional semantic guidance.

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 action ('Retrieve a list') and the resource ('folders in a user's collection'). It is specific and distinguishes from sibling tools like 'get_user_collection_folder' which implies a single folder.

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 guidelines are provided on when to use this tool versus alternatives such as 'get_user_collection_folder'. There is no mention of prerequisites, query parameters, or scenarios where this tool is preferable.

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