create_asset_group_invite

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

No annotations are present, and the description only states the basic invite action. It does not disclose that this likely sends an email (indicated in the schema's 'message' field), any required permissions, or what happens on success/failure. This is a significant gap for a mutating action.

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 a single sentence that is concise and front-loaded with the action, containing no extraneous information.

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?

While the schema is rich and the description covers the essential purpose, it lacks information about the response/return value and side effects like email sending. For a create operation with no output schema, some additional context would be beneficial, but the tool is relatively simple.

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 high (80%), so the schema already explains most parameters. The description adds the concept that email and membership_id are alternative invitation methods, which is helpful. However, it doesn't add detail beyond that.

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 uses a specific verb 'Invite' and clearly states the target (user via email or existing membership) and the resource (collection/lightbox/storage folder). This clearly distinguishes it from sibling tools like list/get/update/delete_asset_group_invite.

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 implies the tool is for creating a new invite but does not explicitly state when to use it versus alternatives such as update_asset_group_invite or list_asset_group_invites. No exclusions or conditions are given.

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