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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds crucial access restrictions (FREE businesses blocked) which goes beyond annotations. However, no mention of pagination behavior or rate limits, which would be expected for a list operation.

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?

Four sentences, each serving a purpose: purpose, then three sentences of usage guidelines. No redundant information. Efficient and well-structured.

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?

Missing output schema means description should explain return values for list result. Also, parameter semantics are incomplete. However, access restrictions are well covered. Adequate but has gaps.

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 0% and description does not explain any parameters (chatId, communityId, batchSize, previousObjectId). The description implies chatId identifies the chat, but communityId purpose is unclear, and pagination params are undocumented. With no schema descriptions, the description should compensate but does not.

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?

Clearly states 'List messages for an AI Cofounder chat' with a specific verb (list) and resource (messages). Distinguishes from sibling tool 'list_ai_cofounder_chats' which lists chats, not messages.

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?

Provides explicit when-to-use and when-not-to-use guidance: check business permissions, FREE businesses cannot use, call check_business_tool_access first, show warnings and resubscribe link, never proceed when blocked. This is actionable and comprehensive.

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