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

Annotations already declare readOnlyHint=true, so no destructive behavior. The description adds context that the tool operates in a community managed by the authenticated user and that free businesses are blocked. It also details the permission-checking workflow. This provides meaningful behavioral context beyond 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 4 sentences long and contains important preconditions, but it could be more concise. The first sentence clearly states the tool's purpose, but the subsequent instructions are lengthy and could be separated or abbreviated. Still, the information is well-organized and front-loaded.

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 should ideally mention what the response contains, especially for a read tool. The description only states 'Get a single physical product order' without detailing returned fields. However, it comprehensively covers permission and access context. Lacks completeness regarding return value but adequate for a simple retrieval.

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 0% description coverage, so the description must explain parameter meanings. However, the description only mentions that the order is 'in a community managed by the authenticated Nas.com user' and does not clarify individual parameters (communityId, productId, orderId). The agent must infer from names, which is insufficient for a tool with no 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 a single physical product order in a community', which specifies the verb (get) and resource (order). It distinguishes from siblings like list_physical_product_orders and get_physical_product. However, the purpose is mixed with extensive usage guidelines, slightly diluting clarity.

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 instructions: check business permissions, free businesses cannot use, call check_business_tool_access before inputs, show grace-period warnings, and never proceed when access is blocked. This clearly delineates 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.