clickup_guest_get

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

Discloses plan requirement and that it returns a guest object. No annotations provided, so description carries full burden. Could mention authentication scope or potential errors, but adequate for a read operation.

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 concise sentences: action with result, guest definition, plan requirement. No redundant words; all content is relevant.

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 purpose, return type, plan constraint, and parameter sources. Schema coverage is 100%, so description complements well. Could mention error handling but not essential for a simple retrieval tool.

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?

Adds valuable guidance beyond schema: explains how to obtain guest_id (from guest_invite) and team_id (from workspace_list), including default behavior for team_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?

Clearly states it fetches a guest profile with specific fields (email, permissions, shared items). Distinguishes from sibling tools like guest_invite or guest_remove by focusing on retrieval.

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?

Provides context about guests being external collaborators and requires Enterprise plan. Offers parameter sourcing guidance (from guest_invite, workspace_list). Does not explicitly mention when not to use or compare to siblings like guest_update.

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