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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description goes beyond that by disclosing the outbound email side effect, the human-confirmation requirement, and the API-key prerequisite. It stops short of covering duplicate-invite behavior or revocability, so not a 5.

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 purpose is front-loaded, but 'They get an email' and 'Gives one person access to the deck and emails them' say the same thing twice, and the confirmation/auth sentences are stacked without structure. Several sentences do not earn their place.

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 three-parameter mutation tool with no output schema, the definition covers auth requirements, the confirmation gate, and the email side effect, which is enough to call it correctly. Missing details on what happens to an existing collaborator's permission leave a modest gap.

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 100% and all three parameters are documented there, including the can_edit/can_view enum. The description merely restates the permission values, adding no syntax, format, or edge-case meaning beyond the schema.

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 (invite someone by email to edit or view a presentation) and names the core action clearly. It does not, however, distinguish itself from siblings like create_share_link, list_collaborators, or remove_collaborator, so the agent must infer the boundary from the name alone.

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?

It supplies useful operating context (confirm before each call, confirmation can be switched off, needs a Cotlet API key with app access) but never states when to prefer this tool over alternatives such as creating a share link or listing existing collaborators. Usage is implied rather than delimited.

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