shopify_verify_product_readiness

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read' and effect='read'. It adds valuable behavioral detail beyond annotations: the governed host verifies multiple surfaces, returns no raw storefront HTML, and requires the effect to be 'read' with Spring verification. This is substantive context without contradicting the annotations.

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 opening sentence is front-loaded with the core purpose and key constraints. The parameter list is long but justified given the schema provides no descriptions; each parameter definition earns its place. Minor verbosity in repeating 'required' and the awkward 'effect: Required and must be read; Spring verifies it' phrasing keep it from a 5.

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?

For a 13-parameter verification tool, the description covers the necessary inputs, expected formats, and safety behavior; an output schema exists, so return-value documentation is not required. Missing pieces are explicit alternative routing and clarification of the discrepancy between prose-required fields and schema-required fields, but the definition is largely complete for invocation.

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 does heavy lifting and provides strong semantics: exact formats for product_id (numeric or GID), price (two-decimal), currency (uppercase ISO-4217), landing_url (canonical HTTPS), and publication_completed_at (UTC). However, it labels many parameters as 'required' while the input schema only requires 'effect', which could mislead an agent into over-constraining invocation.

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 opens with a specific verb and resource: 'Read exact Shopify Admin and storefront evidence after publication.' It clearly enumerates what gets verified (product, publications, title, price, currency, landing page, checkout surface) and even states a negative ('without returning raw storefront HTML'), making it easy to distinguish from other shopify_* tools.

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 gives clear timing context: this is a post-publication verification step, and the 'governed host verifies' phrasing signals a controlled read workflow. It does not name alternatives or explicitly state when-not-to-use, but the 'after publication' framing plus the distinctive verification scope provides good guidance.

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