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

The annotations already indicate readOnlyHint=true, so the description's claim of checking admin status aligns. It adds valuable behavioral context beyond annotations, such as the prerequisite of calling check_business_tool_access and the restriction on FREE businesses. No contradiction with 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 front-loaded with the purpose but includes several important instructions. It is slightly verbose (e.g., the interchangeability note could be more concise), but every sentence adds value for correct usage.

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?

Given the absence of an output schema, the description adequately covers the tool's purpose, workflow prerequisites, and restrictions. It does not explain the return value format or the exact parameter formatting, but for a read-only tool with 2 parameters, it is fairly 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?

With 0% schema description coverage, the description adds meaning by stating that 'emails' can be one or more and that 'communityId' refers to the business context (since business and community are interchangeable). However, it does not clarify the format of the emails parameter (e.g., comma-separated).

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 tool checks admin status for one or more emails. However, it does not distinguish between this tool and the sibling get_community_admin_status, despite mentioning that 'business and community refer to the same thing and are interchangeable,' which could cause 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?

The description provides explicit guidance on when to use the tool: before offering the action, check business permissions, call check_business_tool_access first, and show grace-period warnings. It also notes that FREE businesses cannot use this tool, which helps the agent decide when to invoke it.

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