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

The annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context: the tool requires a permission pre-check, returns merged activity logs, and has access restrictions for FREE businesses. This goes beyond what annotations provide, though the meaning of 'merged' could be elaborated.

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 well-structured, starting with the core purpose and then providing essential usage guidelines. It is slightly verbose due to repeated warnings but remains clear and efficient. Every sentence adds value, though some redundancy could be trimmed.

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 moderate complexity (2 required params, read-only) and the absence of an output schema, the description could be more complete. It explains the access constraints but does not describe the format or fields of the returned activity logs, leaving the agent partially informed about the output.

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%, so the description must explain the parameters. It only mentions 'for one member' but does not detail communityId or membershipId, leaving their semantics unclear. The agent would need to infer that membershipId identifies the member, but no explicit link is made.

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 retrieves merged activity logs for one member in a managed community, and clarifies that business and community are interchangeable. However, it does not explicitly differentiate it from closely related sibling tools like get_community_member_activity or list_business_activities, relying on the qualifier 'for one member' to distinguish from listing 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?

The description provides explicit guidance on when to use the tool, including a prerequisite to check business permissions with check_business_tool_access, and specifies that FREE businesses cannot use it. It also instructs to show grace-period warnings and never proceed when access is blocked, giving clear usage boundaries.

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