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

Annotations (readOnlyHint=false, destructiveHint=false) are minimal. Description adds context about authorization and usage restrictions (FREE businesses cannot use) but fails to disclose side effects like overwriting existing cover media or return format. Average transparency.

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 functional but somewhat lengthy with repeated warnings. It is front-loaded with purpose and then guidelines, but could be more concise. Every sentence adds value, but there is room for trimming.

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?

Lacks information about return values (no output schema), synchronicity, or what generating cover media entails. Only prerequisites are covered. Given the tool's complexity and missing schema coverage, the description is incomplete.

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 has 2 parameters (productId, communityId) with 0% description coverage. Description provides no explanation of what these parameters represent or how they are used. The description should compensate but does not.

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?

Description states 'Generate cover media assets for a managed physical product' – a specific verb-resource pair. It clearly distinguishes from sibling tools like create_physical_product or publish_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 preconditions: check business permissions, FREE business restriction, call check_business_tool_access before collecting inputs, show grace-period warning, and never proceed when blocked. Clearly tells when to use and what steps to follow.

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