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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's role in behavioral transparency is reduced. The description adds permission-related context but does not disclose behaviors like what happens if no chat is available, return format, or side effects. 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 purpose and followed by usage guidelines. Every sentence adds value, though the guidelines section is somewhat lengthy for a simple read tool. Could be slightly more concise but not overly verbose.

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 simplicity (2 params, no output schema, read-only), the description covers purpose and usage guidelines reasonably. However, it lacks parameter explanations and does not describe the return value or behavior when no chat is available. It also doesn't distinguish from sibling tools. Adequate but with 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?

The input schema has two required string parameters (communityId, recipientLearnerObjectId) with no descriptions (0% schema coverage). The description does not explain what these parameters represent or their expected values, leaving agents to infer from parameter names alone.

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 title and description clearly state the tool gets or locates an available chat for a community manager. It uses specific verbs ('get or locate') and a specific resource ('available chat for a community manager'). However, it does not differentiate from sibling tools like initialize_chat_for_cm or list_community_chats_for_cmp, leaving some ambiguity.

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 when-to-use guidance: check business permissions, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when access is blocked. This clearly defines prerequisites and constraints.

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