Invite User to Organization

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description adds genuinely useful context: that it mutates Calendly state, that it requires confirm=true for the specific action, and that it needs the organizations:write scope. These are exactly the non-obvious behavioral facts an agent needs before invoking a destructive 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?

Three short, front-loaded sentences with no filler; the constraint facts appear immediately after the purpose. It is efficiently sized for the information it conveys, though the opening tautology slightly wastes the prime position.

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 destructive, non-idempotent write tool with no output schema, the description covers the critical constraints: state mutation, the confirm requirement, and the required scope. Given the schema fully documents parameters, this is close to complete, missing only explicit routing to sibling tools.

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 the schema fully documents all six parameters including the confirm flag and payload alternative. The description adds no parameter-level detail beyond what the schema already carries (e.g., it doesn't explain how email vs payload vs payload_file interact), so the baseline of 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?

The first sentence restates the title verbatim ('Invite User to Organization'), so it adds essentially no information beyond the name. The verb+resource is nonetheless clear and distinct from siblings like remove_from_organization or revoke_organization_invitation. It sits between vague and clear because the name carries the differentiation, not the description.

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?

There is no statement of when to use this versus alternatives (e.g., create_invitee, list_organization_invitations, revoke_organization_invitation) or any preconditions. The only conditional content is the confirm=true gate, which is a mechanism rather than usage guidance. A reader can infer the intent from the name but the description itself supplies nothing.

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