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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by disclosing that FREE businesses cannot use the tool regardless of feature rows, and that access must be verified, which is 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 with multiple sentences, each adding value. It front-loads the purpose but includes some redundancy about business/community interchangeability. Still, it earns its length without excess.

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 no output schema, the description lacks information about what the summary contains (e.g., metrics, format). It also fails to explain parameter usage. While prerequisites are covered, the overall completeness is low for a 2-parameter tool with no output schema.

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 2 parameters (date, communityId) with 0% schema description coverage. The description does not explain the meaning, format, or constraints of any parameter. It only implies time range via 'monthly', failing 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 'Get the monthly summary for a managed community' with the verb 'get' and resource 'monthly summary'. It clarifies that 'business' and 'community' are interchangeable, but does not explicitly differentiate from the sibling tool 'get_community_summary', leaving potential ambiguity.

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: check business permissions, call check_business_tool_access before use, handle grace-period warnings and resubscribe links, and never proceed when blocked. It does not discuss alternatives like when to use check_business_summary_exists, but the preconditions are well-defined.

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