clickup_edit_guest_on_workspace

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

Adds patch semantics ('Only fields you pass are sent'), plan restriction ('Enterprise plan only'), and error handling (403, 404). Annotations already provide idempotentHint and destructiveHint, but description adds significant context.

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?

Well-structured with clear sections, no redundant sentences. Efficient and front-loaded with key information.

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?

Covers all necessary aspects: purpose, partial update behavior, plan limitation, usage guidance, return format, and error handling. Output schema exists, so return details are sufficient.

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% per context, so description should explain parameters. It lists some fields in 'When to Use' and provides an example, but does not enumerate all available parameters (e.g., can_edit_tags, custom_role_id). Adequate but not thorough.

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 'Update an existing guest's permission flags or custom role on a Workspace' with specific verb and resource. Distinguishes from sibling tools like add_guest_to_*.

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?

Explicit 'When to Use' and 'When NOT to Use' sections, naming alternatives (per-task/list/folder tools). Provides clear context for when to use this tool.

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