get_user_collection_folder

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('retrieve'), but does not disclose side effects, authentication requirements, rate limits, or error handling. The minimal description adds little beyond the verb itself.

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 sentence, which is concise, but it lacks structure or front-loading of key information. It could be expanded to include more detail without sacrificing 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?

Given no output schema, no annotations, and many sibling collection-related tools, the description is insufficient. It does not explain what metadata is returned, error conditions, or how this tool fits into a workflow (e.g., after getting list of folders).

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%, and the description does not elaborate on any parameters. The two required parameters (username, folder_id) are unexplained, leaving the agent with no guidance on formats, constraints, or how to obtain the folder_id.

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 'Retrieve metadata about a folder in a user's collection', which includes a specific verb and resource. It effectively distinguishes this tool from siblings like create_user_collection_folder, edit_user_collection_folder, delete_user_collection_folder, and get_user_collection_folders (plural).

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?

The description implies that this tool is for retrieving folder metadata, but it does not provide explicit guidance on when to use it versus alternatives like get_user_collection_folders (list all folders) or get_user_collection_items (items in a folder). No exclusions or context is given.

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