Create Folder Sharing

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

Adds meaningful context beyond the annotations: it discloses the required token scope, the delegate_to_contact_permissions fallback, the mandatory confirm=true flag, and warns that the call 'may share access, notify people or incur provider charges.' That last point is a valuable non-obvious side effect that the destructiveHint annotation alone does not convey.

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 opening sentence front-loads the core action and is efficient. The permissions block is longer than ideal but each line carries operative constraint information (scope, delegation, confirm), so nothing is clearly wasted.

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?

For a mutation tool with no output schema and a nested schema, the description covers the authorization model, the confirm gate, and side-effect risk. It omits any note about the payload/payload_file vs body-flags mutual exclusion, but the schema itself documents that constraint.

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 description coverage is high (83%), so the schema already documents confirm, account, folder_id, and the nested sharing fields including defaults. The description only gestures at 'email ... and other optional parameters,' adding little beyond the structured 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?

States a specific verb and resource ('Creates a new sharing object for a folder') and identifies the key input (recipient email). It is distinguishable from update_folder_sharing/delete_folder_sharing by the 'creates new' framing, though it never explicitly names those siblings.

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 on required permissions and the confirm=true prerequisite, which are real usage conditions. However, it gives no guidance on when to use this versus update_folder_sharing or the other sharing siblings, so the alternative-selection question is left to inference.

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