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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds minimal behavioral context beyond the business/community equivalence and the list action, without detailing pagination, ordering, or response format. It does not contradict 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 core purpose and is reasonably concise. The prerequisite instructions are somewhat lengthy but necessary for correct usage. Minor redundancy in explaining business/community interchangeability could be tightened.

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 complexity of five parameters with no schema descriptions and no output schema, the description is incomplete. It lacks parameter documentation and return value information, leaving the agent with significant knowledge gaps despite good usage guidelines.

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?

Schema description coverage is 0%, and the description provides no explanations for any of the five parameters (search, batchSize, onlyUnread, communityId, lastObjectId). The agent cannot infer parameter meanings from the description alone, severely impairing correct usage.

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 lists chats for the community manager inbox, with a specific verb and resource. However, it fails to differentiate from the sibling 'list_community_chats_for_cmp', which appears identical given the claim that 'business and community refer to the same thing'.

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, actionable guidance: it stipulates that FREE businesses cannot use this tool, requires calling 'check_business_tool_access' before inputs, and instructs the agent to show warnings and resubscribe links and never proceed if blocked. This clearly addresses when and how to use the tool.

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