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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds the auth scope requirement ('Needs read_content') and the underlying endpoint (GET /api/3.0/pages.json), which is exactly the kind of context annotations don't carry. It does not mention result shape, but the schema covers pagination.

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?

Three short sentences with the core purpose front-loaded and zero filler. The auth scope and endpoint each earn their space as information unavailable elsewhere in the same form.

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 zero-required-param read-only list with full schema coverage and annotations, the definition is adequate. But with no output schema, an agent has no idea what a 'page' object contains or what identifiers it can carry forward, which the description could have sketched in a clause.

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 100%; both 'page' and 'limit' have defaults, ranges, and a next_page handoff note in the schema. The description adds nothing about parameters, 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 and resource: 'List the store's content pages.' An agent can distinguish this from easystore_list_articles, easystore_list_blogs, and easystore_list_collections by the word 'pages', though the description never explicitly contrasts those similar listing siblings.

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?

'Needs read_content' provides a real prerequisite for use, but there is no guidance on when to prefer this over easystore_list_articles or easystore_list_blogs, nor any exclusion or alternative routing. Usage is implied by the resource name alone.

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