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

Annotations already declare readOnly=false, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered; the description goes beyond that with genuinely behavioral facts: one-use semantics, seven-day expiry, the returned code being secret, access-level requirements, and a credential-retention warning. This is substantive context not derivable from the structured fields.

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?

Purpose and expiry are front-loaded in the first sentence, and the security constraints follow in a logical order. It runs slightly long and the credential-retention warning largely duplicates the key parameter's schema text, but no sentence is wasted.

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 three-parameter mutation with no output schema, the description covers purpose, lifecycle, access requirements, authentication options, and even the nature of the returned value (a secret invitation code). Nothing an agent needs to invoke it correctly is missing.

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 67%: the key and request_id parameters already carry their own explanations, while community_id has no schema description. The description elaborates on the key/Authorization option but adds nothing about community_id, so it neither compensates for the gap nor adds meaning beyond the schema.

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 and resource ('Create a one-use invite for a private community') with immediately distinguishing attributes (single-use, seven-day expiry). An agent can separate it from the sibling community_invite_revoke without opening either schema.

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 precondition context: 'Requires owner or moderator access and account scope.' This tells the agent when the call will succeed, but it never names an alternative tool or the inverse operation (revocation), so the routing guidance is implicit rather than explicit.

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