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

Goes well beyond the annotations by disclosing that the email is sent externally to recipients from the user's studio, that it requires the user's Cotlet API key with app access, and that confirmation is applied by default. These are exactly the side-effect and auth facts an agent needs before invoking a non-destructive but externally visible write.

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 tool identity, but the first two sentences restate the same 'branded email invite with gallery link' fact, which is redundant. The remaining sentences (studio origin, confirmation default, auth) 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 3-parameter send tool with no output schema, the description covers purpose, recipients, optional note, external side effects, confirmation behavior, and auth requirements. It could still say what a successful call returns (e.g., confirmation of send), but the essentials are present.

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%, so both the recipient list and optional personal note are already documented in the schema. The description mentions 'the addresses you give' and 'an optional personal note' but adds no format, limit, or validation detail beyond the schema, so 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 (send) and resource (branded email invite with the gallery link to clients), clearly distinct from siblings like pixieset_send_invoice or pixieset_create_collection. The purpose is unambiguous, though the core idea is stated twice in slightly different words rather than refined.

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 operative context: confirmation is on by default but can be switched off, and the action 'reaches other people' so the user should confirm each call. It does not name an alternative tool, but no obvious sibling competes for this share-invite action, so the routing need is low.

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