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

Annotations already indicate readOnlyHint=true, so the read-only nature is covered. The description adds valuable behavioral context beyond annotations by detailing access control nuances (FREE businesses cannot use, need to check business permissions) and required pre-checks. No contradiction with 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 concise (5 sentences) with a clear structure: first states purpose, then lists prerequisites and constraints. All information is relevant and earns its place. Slight redundancy in 'before offering this action or requesting its inputs' could be trimmed, but overall efficient.

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 tool is simple (2 required params, no output schema), but the description omits what the tool returns (e.g., full product details, fields). Without an output schema, agents lack information on return structure. Access prerequisites are well-covered, but missing output details reduces completeness.

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% (no descriptions in schema), and the description does not explain the two parameters (productId, communityId). It only implies their existence via the phrase 'for a community'. This forces the agent to infer parameter meanings, which is insufficient.

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 the tool retrieves 'editable physical product details for a community', specifying the verb (Get), resource (physical product details), and scope. The term 'editable' hints at distinction from read-only views like get_physical_product_inventory, but does not explicitly differentiate it from all siblings, which is acceptable for a getter.

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 usage guidance: check business permissions, note that FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, show grace-period warnings, and never proceed when access is blocked. This clearly outlines when and how to use the tool, including prerequisites and restrictions.

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