Get Organization Invitation

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the concrete auth requirement 'Required scopes: organizations:read', which is real operational context not present in the annotations or schema. It stops short of noting error behavior for missing/nonexistent invitations.

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 fragments with no padding, and the scope requirement is easy to find. 'Reads Calendly data' is redundant with the tool name but costs only a few words.

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 simple read-by-id tool with full schema coverage and rich annotations, the description plus structured fields are sufficient to invoke it correctly. The remaining gap is that no output schema exists and the description says nothing about what an invitation record contains or what happens on a bad UUID.

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 all three parameters (account, org_uuid, invitation_uuid) are already documented in the schema with types, patterns and roles. The description adds nothing about parameter meaning or interaction, 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?

The first sentence restates the tool name verbatim, adding no scope or resource detail beyond the title. 'Reads Calendly data' is generic filler that does not distinguish this tool from the many sibling read tools (e.g. list_organization_invitations, get_organization_membership).

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?

No guidance on when to call this versus siblings such as list_organization_invitations (which lists many) or revoke_organization_invitation (which acts on one). The agent must infer usage entirely from the name and required parameters.

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