Get Shopify Page by ID

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds what the payload contains (HTML body, SEO, publish status), which is modest value beyond the annotations, but says nothing about auth scope, errors, or how large the body may be.

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?

Two short sentences, front-loaded with the return-content summary and followed by the usage hint. Nothing is redundant or padded.

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?

A single-parameter read tool with annotations and no output schema; the description covers what a caller wants to know (payload contents and when to reach for it). Only minor gaps remain around pagination/error behavior, which are largely irrelevant here.

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 100% schema description coverage, the schema already documents the single pageId parameter including the GID format example. The description adds no parameter-level detail such as format expectations or ID sourcing, so the baseline 3 applies.

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?

States a specific verb+resource (get a specific page) and enumerates what the response contains: HTML body, SEO, publish status. It differentiates from the sibling list tool by naming shopify_get_pages as the entry point rather than a competitor.

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?

Gives explicit sequencing guidance: 'Use after shopify_get_pages to get the full body of a specific page.' This tells the agent when this tool is the right next step. It stops short of naming when NOT to use it or listing edge cases.

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