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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the annotation carries the safety profile. The description adds the returned field set and the cross-tool meaning of `page.id`, which is useful context, but says nothing about pagination behavior, ordering, or limits beyond what the schema states.

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 tight sentences: the returned fields come first, then the high-value note about page_id, then the endpoint. No filler, no restating of the tool name.

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, enumerating the returned fields is exactly the right compensation, and the page_id linkage closes the loop for downstream tools. Minor gap: pagination semantics (how to walk pages, what happens past the last page) are implied only by the schema parameters.

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%, so `page` and `per_page` are already fully documented with defaults and max. The description adds no parameter-level meaning (e.g., ordering of results across pages), so the baseline of 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 all status pages on the account') plus the exact fields returned, and pairs it with the underlying endpoint (GET /v2/pages). This clearly distinguishes it from sibling list tools such as instatus_list_components and instatus_list_incidents.

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?

Explains the role this call plays for the rest of the toolset: 'The page id is what every other tool takes as `page_id`', which tells the agent to resolve page ids here first. It does not state any when-not conditions or exclusions, but for a leaf list tool none are really needed.

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