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

Annotations already mark it read-only, and the description adds real behavior beyond that: preview does not consume the invitation, and specific failure conditions surface as organization_invitation_invalid with a no-retry instruction. It does not cover rate limits, caching, or what invalid-but-valid-format tokens look like, keeping it short of 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?

Front-loaded with the core action and scope, then the flow, then input format, then error handling — every clause carries information and there is no filler. The arrow-chain phrasing is dense but readable and appropriately sized for a two-step protocol.

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?

With no output schema, the description could say more about what the preview returns (org identity, terms text location, validity), but it fully covers the call protocol, the token format constraint, non-consumption, and the failure mode. Enough to invoke correctly, slightly light on the response side.

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 coverage is 100%, so the baseline is 3; the description still adds value by stressing the token must not be truncated (43 chars or the full link) and by tying includeTermsBody to the consent→apply flow with the same token. It largely restates the schema's field meanings, which caps it below 5.

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+resource (preview an organization invitation), adds the key scope qualifier that it works anonymously and for private orgs, and explicitly links to the sibling apply_to_organization as the follow-up step. An agent can distinguish it from apply_to_organization / respond_organization_invite immediately.

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 an explicit flow: pass includeTermsBody=true to show the agreement, get user consent, then call apply_to_organization with the same invitationToken for auto-approval. It also says not to retry on organization_invitation_invalid (expired/revoked/issuer lost rights), which is a concrete when-not-to-use rule.

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