remove_guest_from_folder

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

No annotations are present. The description states 'revoke access', implying a destructive action, but it does not disclose side effects, required permissions, reversibility, or what happens if the guest or folder doesn't exist. More transparency is needed.

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 extremely concise with two short sentences, no redundancy, and front-loads the primary action. Every word serves a purpose.

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?

The tool is simple with two parameters and no output schema. The description covers the basic action but lacks details on error handling, prerequisites, or behavior. It is minimally adequate but not comprehensive.

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?

The input schema describes folder_id with 'Folder ID.' but guest_id has no description. Schema description coverage is 50%. The description does not add meaning beyond the schema for guest_id, leaving ambiguity about its format or purpose.

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 action ('revoke a guest's access') and the resource ('Folder'), and it distinguishes from sibling tools like remove_guest_from_list and remove_guest_from_task by specifying 'Folder'. The additional 'Enterprise only' scoping adds clarity.

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 includes 'Enterprise only', which indicates a usage constraint, but it does not provide guidance on when to use this tool over alternatives (e.g., when to use remove_guest_from_folder vs remove_guest). No exclusions or context are given.

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