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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds important behavioral context beyond annotations, such as business permission checks and restrictions for FREE businesses, plus guidance on handling grace periods and resubscribe links, enhancing agent understanding of preconditions and actions.

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 concise at 4 sentences, covering purpose and usage guidelines without unnecessary details. It could benefit from more structured formatting (e.g., bullet points), but the information density is good and front-loaded.

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 required params, no output schema), the description adequately covers purpose, preconditions, and behavioral requirements. It does not describe the return value, but since no output schema exists, the omission is acceptable. The description is complete enough for an agent to understand when and how to invoke the tool.

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 has 2 parameters (communityId, hostObjectId) with 0% description coverage. The description does not explain what these parameters represent or any constraints beyond the schema's minLength. The parameter names are self-explanatory, but the description should have provided additional context to compensate for the lack of schema descriptions.

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 action: Get host profile information for a one-on-one session host in a managed community. It uses a specific verb and resource, and distinguishes itself from sibling tools like 'get_session' and 'get_member' tools.

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?

Explicitly instructs to check business permissions first, warns that FREE businesses cannot use the tool, and directs to call 'check_business_tool_access' before collecting inputs. Also describes required user interaction with grace-period warnings and resubscribe links, providing comprehensive when-to-use guidance.

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