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

Annotations indicate readOnlyHint=false, but the tool name and description imply a read operation (extracting metadata). The description adds behavioral context about permissions and business restrictions, but does not clarify whether the tool is truly non-read-only or what side effects occur. This partial but incomplete transparency yields a 3.

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 short, front-loaded with purpose, and each sentence provides necessary instruction. No wasted 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?

With no output schema, the description should indicate what metadata is returned but does not. It also fails to explain the 'communityId' parameter. The permissions context is useful but insufficient for a complete understanding of the tool's input/output behavior.

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 description coverage is 0%, so the description must compensate. It mentions the 'url' parameter implicitly but does not explain 'communityId' or provide any parameter details beyond the schema. The description adds minimal value to the schema, resulting in a low score.

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 'Extract metadata for an external product URL', providing a specific verb and resource. It is distinct from siblings like 'update_external_product' and 'create_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?

The description explicitly instructs to check business permissions before use, identifies free business restriction, directs to call 'check_business_tool_access', and warns about grace-period and blocked access. This provides excellent when-to-use/when-not-to-use guidance.

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