clickup_guest_share_list

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

With no annotations provided, the description carries the full burden. It discloses that guests are external collaborators (not paid seats), explains the scoping effect, requires Enterprise plan, and states the return (updated guest object). It doesn't mention whether permissions are additive or replace existing, but overall provides solid behavioral 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?

The description is concise with two well-structured sentences. The first sentence states the core action, and the second adds essential context (guest definition, revocation alternative, plan requirement, return). No redundant information or fluff.

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 the tool's simplicity (3 required params, no output schema, no annotations), the description covers key aspects: what the tool does, what a guest is, plan limitation, and forward reference to the unshare tool. It could mention whether sharing is incremental or replaces existing permissions, but overall it's sufficient for correct usage.

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 detailed descriptions for all three parameters. The description adds value by providing sourcing hints (e.g., 'Obtain from clickup_guest_get') and clarifying permission level meanings beyond the schema. This enhances the agent's understanding of how to correctly populate the 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?

The description clearly states the tool's purpose: granting a ClickUp guest user access to a list with a specific permission level. It uses specific verbs ('grant', 'scope') and identifies the resource ('guest user', 'list'), distinguishing it from sibling tools like clickup_guest_unshare_list.

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 explicitly mentions when to use (grant guest access to a list) and references the complementary tool for revocation (clickup_guest_unshare_list). It also notes the Enterprise plan requirement. However, it does not explicitly exclude alternatives like sharing a folder instead, but the context is clear for this specific operation.

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