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

Beyond the destructiveHint annotation, the description specifies the required confirm value, mandatory permission checks, free business restriction, and warning display, adding actionable behavioral context.

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?

Every sentence adds value: the first states the action, the second specifies the confirm requirement, and the remaining provide mandatory preconditions. No unnecessary words.

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 permissions, access checks, business type restrictions, and warning display adequately. Lacks explicit description of the publish effect (e.g., making product available) but the action is clear from context.

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?

With 0% schema description coverage, the description only mentions that confirm must be set to 'PUBLISH', leaving productId and communityId unexplained. The input schema has no descriptions, so this is insufficient for a critical action.

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 explicitly states 'Publish a physical product' and adds critical prerequisites (confirm field, permission checks, free business restriction), clearly distinguishing it from sibling tools like create_physical_product or unpublish_physical_product.

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 steps: check business permissions, call check_business_tool_access, show grace-period warning, and never proceed when blocked. This gives clear guidance on when and how to use the tool, implicitly differentiating from creation/update/unpublish.

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