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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is clear. The description adds useful context about permission checking and business restrictions, but does not describe the output format, pagination behavior, or any potential side effects beyond the prerequisites.

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 purpose and includes essential procedural instructions. It is slightly verbose due to the interchangeability clarification and repeated permission checks, but overall it is well-structured without unnecessary 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?

For a tool with 5 parameters, no output schema, and no param descriptions, the description covers prerequisites but lacks critical details: what the parameters do, pagination using lastObjectId, response format, and error scenarios. The agent would struggle to use this tool correctly without additional knowledge.

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 input schema has 5 parameters with 0% coverage (no descriptions). The description does not explain any parameter meanings (e.g., search, batchSize, onlyUnread, lastObjectId). It only indirectly references communityId. With no compensation, the agent has no guidance on parameter semantics.

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 states it lists community chats for the community manager inbox, which is a specific verb and resource. However, it adds that 'Business and community refer to the same thing and are interchangeable,' introducing potential confusion with the sibling tool 'list_business_chats_for_cmp' and failing to differentiate between them.

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 guidelines: check business permissions first, call 'check_business_tool_access' before collecting inputs, show grace-period warnings and resubscribe links, and never proceed when access is blocked. It also states that FREE businesses cannot use this tool, giving clear when-not-to-use conditions.

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