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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description adds context about free business restrictions and required pre-checks. No contradiction with annotations; the description enriches the understanding of behavioral constraints beyond what annotations provide.

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 verbose but every sentence adds important operational context (permissions, restrictions, prerequisites). It could be slightly more concise, but it is well‑structured and front‑loaded with the core purpose.

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?

The description covers the essential behavioral context for a read‑only tool with one parameter: business type distinction, free business restriction, required pre‑checks, and warnings. While it does not describe the return format, the lack of an output schema may imply simple output; overall, it is sufficiently complete for its complexity.

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?

There is only one parameter, communityId, which is self‑explanatory from its name and type. However, with 0% schema description coverage, the description does not add any semantic details about the parameter (e.g., format, source, or validation). It meets the baseline for a simple, single parameter but does not compensate for the lack of schema 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 tool's purpose: 'Get current admin count and limit for a managed community.' It also explains the interchangeable use of 'business' and 'community,' which helps differentiate from sibling tools that deal with admin management or counts for other entities.

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?

Explicit guidance is provided: check business permissions first, FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, and show grace-period warnings. This clearly distinguishes when and how to use this tool versus alternatives.

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