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

Annotations already indicate readOnlyHint: true and destructiveHint: false. The description adds valuable behavioral traits: FREE businesses cannot use it, permission checks are required, and there are warnings and links to handle. No contradiction with annotations. The description goes beyond annotations to disclose usage restrictions.

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 four sentences. The first sentence gives the purpose, but the remaining sentences are a sequence of instructions that could be streamlined. It is not overly long but could be more concise without losing essential guidance.

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?

The description focuses heavily on prerequisites but omits what the tool returns. There is no output schema, so the description should explain the return structure or type of items. Without this, the agent lacks information needed to use the result correctly.

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 one parameter (communityId) with 0% description coverage. The description does not explain the parameter's meaning, format, or how to obtain it. Since coverage is low, the description should compensate, but it fails entirely to add semantic value for the parameter.

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 retrieves action center items for a managed community. The verb 'get' and resource 'action center items' are specific. However, it does not distinguish from siblings like 'dismiss_action_center_item' or other get tools, lacking differentiation.

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 prerequisites: check business permissions, call check_business_tool_access, handle grace-period warnings and resubscribe links, and never proceed when access is blocked. It gives clear context for when to invoke the tool but does not compare to alternatives or state when not to use it.

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