edit_guest

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

No annotations provided, so description carries full weight. It discloses partial update behavior ('Only the provided flags change'), return value ('Returns the updated guest'), and plan restriction. Lacks details on permissions or side effects, but acceptable for a simple update.

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?

Two sentences covering purpose, capabilities, behavior, and plan requirement. No wasted words, well front-loaded.

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?

No output schema, but description states returns updated guest. Covers essential behavioral traits for an edit tool, though missing prerequisites like guest existence.

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 parameter descriptions. Description adds 'Only the provided flags change' indicating patch semantics, but otherwise does not elaborate on parameters beyond 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?

Description clearly states the tool edits a guest's Workspace-level capabilities, listing specific capabilities (tags, time visibility, view creation). This distinguishes it from sibling tools like 'invite_guest' or 'remove_guest'.

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?

Includes 'Only the provided flags change' implying partial updates, and 'Enterprise plan only' restricting usage. It does not explicitly list when not to use or alternatives, but context is clear for an updating tool.

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