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

With no annotations, the description carries the behavioral disclosure burden. It reveals the output fields, the live-store source, and the meaningful detail that updatedAt should be passed as expected_updated_at when proposing a page publish. It does not mention pagination or errors, but it gives enough behavioral context for a read-only listing tool.

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 first two sentences are informative and front-loaded, but the 'Routing' line largely repeats the same information as the first sentence. The description is reasonably compact but contains redundancy that a tighter definition would avoid.

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 compensates by enumerating the returned fields for pages and blogs and explaining the intended use case. The two parameters are fully covered by the schema. It could add result ordering or pagination behavior, but it is otherwise adequate for a listing tool.

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 already documents limit and companyId with 100% coverage, including defaults and max values. The description adds no parameter-level meaning beyond a related cross-tool note about updatedAt, which is not itself a parameter of this tool.

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 it lists the connected Shopify store's online-store pages and blogs, including the specific fields returned and the live-store scope. This distinguishes it from sibling tools like list_shopify_products or list_shopify_themes.

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?

It explicitly says to use this tool before drafting a new page or blog post, giving a clear use context. It does not name alternatives to avoid or exclusion criteria, but the intended scenario is well specified.

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