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

Annotations already mark the tool as read-only and non-destructive, but the description adds critical behavioral context: FREE business restriction, access-check requirement, and conditional warnings. No contradiction. Slight deduction for not describing the dashboard's structure or return format.

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?

Five sentences, each with distinct information. Front-loaded with purpose and prerequisite steps. Slightly verbose for a simple getter, but every sentence is useful. Could be tightened without losing meaning.

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 tool's low complexity (1 param, no output schema, read-only), the description covers access constraints, prerequisites, and error handling. Not mentioning the dashboard's data shape is acceptable without an output schema. Overall sufficient for agent understanding.

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 single parameter 'communityId' is not explained in the schema (0% coverage). The description implies its purpose ('for a managed community') but does not explicitly state that it identifies the community. Minimal value added over the parameter name.

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 ('Get') and resource ('community manager home dashboard for a managed community'), and the targeted context ('managed community') distinguishes it from siblings like get_cmp_home_analytics or get_community.

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 when to use: only after checking business permissions, and specifically mentions FREE businesses cannot use this tool. Provides a clear prerequisite action (call check_business_tool_access) and handling of grace-period warnings, leaving no ambiguity about the usage flow.

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