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

Annotations indicate it is not read-only and not destructive. The description adds context about business plan restrictions and prerequisites, but does not fully detail what happens if the tool is called without authorization or the exact response. Still, it provides useful behavioral context beyond annotations.

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?

The description is concise with four sentences. It front-loads the purpose and immediately follows with necessary usage prerequisites, avoiding unnecessary information.

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?

Covers purpose and usage well, but lacks parameter descriptions and clear differentiation from a sibling tool. Given the simplicity of the tool (2 params, no output schema), it is adequate but could be more complete.

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 0%. The description does not explain the 'communityId' or 'emails' parameters, their purpose, format, or how to obtain them. It mentions 'emails' implicitly but does not define the array structure or constraints.

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 description clearly states it invites or adds admin users to a managed community. It uses specific verbs and identifies the resource. However, it does not differentiate from the sibling tool 'add_community_admins', which appears identical, causing potential confusion.

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?

Provides explicit guidance: check business permissions, FREE businesses cannot use, call check_business_tool_access before, show grace-period warning and verified resubscribe link, and never proceed when blocked. This clearly tells when and how to use the tool.

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