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

Annotations already indicate read-only and non-destructive. The description adds crucial behavioral details: permission dependencies, business tier restriction, and required user-facing warnings and actions. 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 concise and well-structured, starting with the purpose and then providing clear, sequential usage instructions. Every sentence adds value with no fluff.

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?

While the description covers preconditions well, it does not describe the return value or structure of the checklist. Since there is no output schema, agents are left without knowledge of what the response contains, which is a gap for a data-retrieval tool.

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?

The sole parameter 'communityId' has no schema description (0% coverage). The parameter name is self-explanatory, but the description does not add any additional semantics, such as where to obtain it or its format. With 0% schema coverage, more parameter context would be beneficial.

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 'Get the business setup/get-started checklist for a managed community,' providing a specific verb and resource. It distinguishes itself from siblings like get_cmp_home by specifying the checklist aspect.

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?

Explicitly instructs to check business permissions before offering the action, notes that FREE businesses cannot use it, calls check_business_tool_access, and provides steps for handling grace-period warnings and blocked access. This is very clear guidance.

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