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

Annotations show readOnlyHint=false and destructiveHint=false, which align with regeneration (a write operation, not destructive). The description adds important behavioral context: permission checks, business restrictions, and required prior steps. It does not contradict annotations and provides transparency about access requirements.

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: four sentences that front-load the purpose and then provide clear usage instructions. Every sentence adds value, with no wasted words. The structure logically flows from what the tool does to how to use it.

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 the tool's complexity (requires permission checks, business tier restrictions), the description is complete. It covers all essential context: action, prerequisite checks, business eligibility, and error handling. No output schema, so no need to explain return values. The description fully equips an agent to use the tool correctly.

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 two parameters (assetId, communityId) with no descriptions (0% coverage). The description does not explain what these parameters represent or their expected values. For example, it doesn't clarify that assetId identifies the creative asset to regenerate, or that communityId specifies the community context. This is a significant gap given the low schema coverage.

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 action: 'Regenerate a product creative asset.' It uses a specific verb and resource. However, it does not differentiate from sibling tools like 'edit_creative_asset' or 'import_creative_asset', which could cause confusion about when to use regenerate versus edit or import.

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 guidelines: check business permissions, note FREE businesses cannot use, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, never proceed when blocked. This clearly tells when and how to use the tool, including preconditions and prohibitions.

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