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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses critical behavioral traits: permission requirements, restriction for FREE businesses, the need to call a prerequisite tool (check_business_tool_access), and handling of grace-period warnings. This adds significant value beyond the 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 relatively concise at around 70 words, front-loading the main purpose in the first sentence. However, the line 'Business and community refer to the same thing and are interchangeable' could be streamlined without losing clarity.

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 has 4 parameters, no output schema, and a complex permission requirement, the description omits many details. It does not explain what the parameters do, what the return value looks like (e.g., list of activity items), or what 'grace-period warning' and 'verified resubscribe link' entail. The focus on workflow leaves the tool's functional context 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 for its 4 parameters (limit, communityId, activityTypes, lastActivityObjectId). The description does not mention any parameter, failing to add meaning beyond the bare schema. For a tool with no schema descriptions, this is a major 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 'List recent activity feed items for a managed community' providing a specific verb and resource. It also clarifies that 'Business and community refer to the same thing', which helps disambiguate but does not explicitly differentiate from the sibling tool 'list_community_activities'.

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 preconditions: check business permissions, FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, and show grace-period warnings. It clearly states when not to proceed, offering strong usage guidance for the AI agent.

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