clickup_guest_update

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

With no annotations, the description fully carries the burden. It explains the tool updates flags, notes plan requirement, mentions return value (updated guest object), and implies non-destructive behavior (omitting param keeps current value). Could add detail on immediacy or reversibility, but sufficient.

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?

Three sentences, no filler. Front-loaded with purpose, then clear exclusion, then plan and return. Every sentence adds essential information 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?

Complete for a simple update tool with no output schema. Describes functionality, constraints, return value, and boundary with sibling tools. Given the parameter count and absence of nested objects, nothing more is needed.

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 100% with each parameter fully described. The description adds context by grouping the flags as 'workspace-wide capability flags' and explaining the return, but does not enhance individual parameter meaning beyond the schema. Baseline 3 is appropriate.

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 verb 'Update' and the resource 'a ClickUp guest's workspace-wide capability flags' with specific examples (edit tags, see time spent, create views). It also differentiates from sibling tools that handle sharing vs capabilities.

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 states when not to use this tool (does not change sharing) and directs to alternative tools (clickup_guest_share_* / _unshare_*). Also mentions the Enterprise plan requirement, providing clear context for invocation.

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