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

Annotations only declare readOnly=false, openWorld=true, destructive=false; the description adds genuinely useful behavior beyond that: anyone with the link can open the deck (public-exposure risk), the default per-call confirmation and how to disable it, and the required Cotlet API key scope. It doesn't cover link expiry or revocation, but the added context is substantive.

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?

Front-loaded with the core action, but the first two sentences are largely redundant ('Share the presentation and return a link to it' / 'Makes the deck viewable through a link and returns the link'). The confirmation and auth sentences carry real weight; the opening repetition does not fully earn its 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 two-parameter action tool with no output schema, the description covers what the agent needs: the side effect (public link), confirmation expectation, and auth requirement. Missing only peripheral details such as link lifetime or revocation behavior.

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 both params (name, presentation_id) are documented in the schema itself. The description adds no additional meaning about the parameters, so the baseline 3 applies.

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 (share) and resource (the presentation) and the concrete outcome (returns a link making the deck viewable). An agent can distinguish this from sibling tools like beautiful-ai_invite_collaborator or beautiful-ai_list_collaborators, which grant named access rather than producing a public link.

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?

Gives clear context: 'By default you confirm each call' and 'Reaches other people: confirm with the user before each call,' plus the auth prerequisite. It does not, however, contrast this with invite_collaborator for the case where the user wants restricted (named) access rather than a public link, so an alternative path is left implicit.

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