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

Annotations already declare readOnlyHint=true and destructiveHint=false, setting a read-only expectation. The description adds valuable behavioral context: access restrictions, prerequisite tool calls, and user-facing warning handling. It does not contradict annotations and enriches the agent's understanding beyond structured fields.

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 (4 sentences) and front-loads the purpose. The structure logically flows from purpose to usage constraints. It is not overly verbose, though there is minor redundancy (e.g., restating the access check).

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 has no output schema, so the description should fill the gap by explaining what 'overview data' includes. It fails to do so, leaving the agent uncertain about the return format or contents. Given low parameter count and no enums, more completeness is expected.

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%, meaning no parameter descriptions are provided. The description also omits any explanation of the two required parameters (productId, communityId), offering no additional meaning beyond the schema's basic type and required status.

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 overview data for a managed physical product. However, it does not differentiate this 'overview' from sibling tools like get_physical_product or get_physical_product_analytics, which could lead to 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 explicitly states when to use the tool (after checking business permissions), when not to use it (FREE businesses cannot use), and provides a precise prerequisite (call check_business_tool_access). It also instructs on handling warnings and blocked access, which is exemplary guidance.

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