create_user_collection_folder

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

Minimal disclosure: implies a write operation (create) but no details on whether it overwrites existing folders, required permissions, or side effects like updating folder counts. No annotations compensate.

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 sentence, no redundancy, but too short; lacks key details that could be included without losing conciseness.

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?

Grossly inadequate for a tool with 2 unannotated parameters, no output schema, and no annotations. Should describe success conditions, naming constraints, and error states.

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 0%, and description adds no meaning to parameters. 'username' and 'name' are not explained; agent must guess their purpose (e.g., username vs folder name).

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 it creates a folder in a user's collection, distinguishing from other new-folder tools like create_marketplace_listing. However, it doesn't explicitly differentiate from sibling edit_user_collection_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 guidance on when to use this tool versus alternatives, such as edit_user_collection_folder for renaming or when the folder already exists. No context about prerequisites or typical use cases.

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