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

Annotations already indicate readOnly and non-destructive. The description adds valuable context: the need for permission checking, business tier restrictions, and specific UI procedures (grace-period warning, resubscribe link). This supplements the annotations well.

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 moderately concise but contains some redundancy (e.g., 'Business and community refer to the same thing and are interchangeable'). It front-loads the core purpose, but the usage instructions take up most of the text. It could be streamlined.

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 the description does not describe the response format or what fields are returned. Additionally, parameter descriptions are missing. For a list tool, the lack of output and parameter details makes it incomplete.

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 0% description coverage, and the description does not explain any parameter semantics. It only mentions that 'communityId' is required but provides no details about other parameters like 'limit', 'activityTypes', or 'lastActivityObjectId'. This is a significant gap.

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 it lists recent activity feed items for a managed community. It also attempts to clarify the interchangeable use of 'business' and 'community', though this might blur distinction with the sibling tool 'list_business_activities'. Overall, the purpose is specific and understandable.

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 prerequisites: check business permissions, note that FREE businesses cannot use it, and call 'check_business_tool_access' before collecting inputs. It also instructs on showing grace-period warnings and resubscribe links. However, it does not compare directly with alternatives like 'list_business_activities'.

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