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

Annotations already confirm read-only and non-destructive behavior. The description adds important behavioral context: free businesses are restricted and an access check is required. This goes beyond annotations by specifying permission constraints and prerequisite steps.

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?

Description is front-loaded with purpose and includes essential instructions, but is somewhat lengthy. The clarification that 'business and community are interchangeable' is helpful but could be more concise. Some redundancy in the access guidance (e.g., 'before offering this action' and 'before collecting inputs').

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?

Covers prerequisites and access control well, but omits output details (no output schema) and does not differentiate from similar tools like check_business_storage. A simple retrieval tool should ideally mention what data is returned (e.g., storage used, limit).

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 coverage is 0%, so description must compensate. Only parameter is communityId, but description does not elaborate on its meaning, format, or examples. It simply implies the identifier for the community. Without additional detail, agents may not understand how to construct the parameter correctly.

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?

Clearly states verb 'retrieve' and resource 'community storage usage information'. Clarifies interchangeability of 'business' and 'community' to avoid confusion. However, does not explicitly differentiate from sibling tools like 'check_business_storage' or 'check_community_storage', though the verb 'get' vs 'check' implies a different operation.

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?

Provides explicit instructions: check business permissions, note that FREE businesses cannot use, call check_business_tool_access before collecting inputs, display grace-period warnings, and never proceed when access is blocked. This gives clear when-to-use and prerequisites, making it highly actionable.

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