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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and the description adds real access-control behavior beyond that: free-tier blocking, a mandatory pre-check call, grace-period warnings and resubscribe links. It does not describe the response shape or whether the result carries a new cursor ID for the next call, which matters for a since-lastObjectId check.

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 purpose is front-loaded in sentence one, but the remaining four sentences are compliance boilerplate with redundancy: 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs' say the same thing twice. Tightening would leave room for return-value semantics.

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?

There is no output schema and no explanation of the return value, yet this is a boolean-with-cursor style check tool where knowing the response shape matters. Access gating is covered thoroughly, so the tool is callable, but the result-handling half of the contract is absent.

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 coverage is 50%: communityId is documented inline, but lastObjectId has no schema description. The phrase 'after an object ID' incidentally reveals that lastObjectId is a cursor, but the description does not explain what the null case means or whether the response returns a value to pass back in.

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 first sentence states a specific verb and resource: check whether a managed community has unread chat messages after a given object ID. The note that business and community are interchangeable helps disambiguate among the similarly named chat siblings (has_new_unread_community_chat, has_unread_business_chat), though it never explicitly says how this 'new unread after an ID' check differs from a plain unread check.

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?

Gives strong precondition guidance: verify business permissions before offering the action, FREE businesses are excluded regardless of feature rows, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. What is missing is tool-selection guidance, i.e. when an agent should pick this over has_unread_business_chat or has_unread_community_chat.

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