ecommerce_seo_optimizer

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that the tool performs parsing and rewriting, which implies mutation of HTML, but it does not explain side effects, what exactly gets rewritten, whether existing schema or SEO tags are replaced, or what the expected output format is. The word 'Fast' adds a performance claim but no actionable behavioral detail.

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 a single, tightly-worded sentence with no filler. It front-loads the core capability ('Fast HTML DOM parsing and rewriting') and immediately states the intended outcome. Every word contributes to the overall meaning, making it easy to parse quickly.

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 has no annotations, no output schema, five parameters, a nested entityData object, and a potentially destructive rewriting behavior, this description is not sufficient. It does not explain what the agent should pass for entityType, how entityData relates to the schema, what HTML is expected, or what the function returns. An agent would struggle to invoke this correctly without additional information.

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 for the schema's lack of explanation. It references 'entity-based JSON-LD schemas', which weakly maps to entityType and entityData, but it does not explain the role of title, description, or htmlString beyond the obvious. It fails to clarify how entityData should be structured, which is especially important given the nested object with additionalProperties.

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 states a clear resource (HTML DOM), a specific set of operations (parsing and rewriting), and the intended outcome (JSON-LD schemas and on-page SEO optimization). It is distinguishable from most ecommerce siblings, and the 'Fast HTML DOM parsing and rewriting' phrasing gives a concrete sense of the mechanism. However, it does not explicitly differentiate itself from the similarly-named ecommerce_ow_lnwshop_safe_seo_updater, so it falls short of a perfect 5.

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 implies this tool is for SEO optimization and JSON-LD generation, but it gives no explicit guidance on when to use it versus the many sibling ecommerce tools. It does not state prerequisites, exclusions, or alternatives, such as when ecommerce_ow_lnwshop_safe_seo_updater would be preferable. An agent would have to infer usage from the tool name and general context rather than from clear instructions.

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