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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses that the tool adds admin users, that business/community are interchangeable, and that it cannot be used by FREE businesses. This provides valuable behavioral context for safe invocation.

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?

Description is well-structured with core purpose first, then clarifications, then usage guidelines. It is informative but could be slightly more concise. Nevertheless, every sentence adds value.

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 write tool with no output schema, the description provides necessary preconditions and usage guidance. It does not detail post-invocation behavior (e.g., return value), but this is unlikely to hinder correct use given the tool's simplicity.

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 0%, but the two parameters (communityId, emails) have self-explanatory names. The description does not explicitly explain these parameters, but the context of 'add admin users to a managed community' makes them understandable. Slight lack of explicit documentation.

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 the verb (invite/add) and resource (admin users to a managed community). It also clarifies terminology (business and community are interchangeable), which resolves potential confusion from the title mismatch.

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?

Description explicitly tells when to use (after checking permissions), when not to use (FREE businesses cannot use), and provides a prerequisite tool (check_business_tool_access). Also specifies to show grace-period warnings and never proceed when access is blocked.

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