clickup_create_folder_view

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

Annotations are present (readOnlyHint=false, destructiveHint=false). Description adds return type (confirmation string with id, name, type, or error string) and error handling (404 meaning wrong folder_id). Does not contradict annotations. Could mention any side effects, but creation tools typically have minimal side effects beyond creating the view.

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?

Very concise and well-structured with clear sections: purpose, when to use, when not to use, returns, example, error handling. Every sentence adds value with no redundancy.

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?

For a creation tool with a comprehensive schema and existing annotations, the description covers usage context, error cases, and return format. Output schema is noted as present, so return details are sufficiently covered. No gaps identified.

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 cover all parameters (schema_description_coverage is high, though context says 0% it appears descriptions are present). The description provides a concrete example of required parameters (folder_id, name, type). This adds value over schema alone but does not detail optional parameters.

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?

Clearly states 'Create a task or page view scoped to a Folder.' Differentiates from sibling tools by specifying when NOT to use and naming alternatives (clickup_create_space_view, clickup_create_team_view, clickup_create_list_view).

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?

Explicitly provides 'When to Use' and 'When NOT to Use' sections, naming specific alternative tools for other scopes. This gives clear selection criteria.

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