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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral detail beyond that, such as the ordering ('its own, then pages other accounts share with it') and the specific data returned (access level, monitor counts). This enriches the agent's understanding 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 description is a single, dense sentence that front-loads the core action ('List the pages this account can see') before adding details. It contains no filler, though it could be slightly rephrased for readability. The content is efficient and earns its place.

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?

Given no parameters, no output schema, and a complex return payload, the description sufficiently specifies what the agent can expect: own pages, shared pages, access level for each, and monitor counts (including down monitors). It even notes the ordering. This is complete enough for an agent to invoke the tool and interpret the result correctly.

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 tool has zero parameters, and schema coverage is 100% (no params). The description therefore does not need to explain parameter meanings, and the baseline of 4 applies. It appropriately focuses on what the tool returns rather than inputs.

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 the action 'List' and the resource 'pages', and specifies the scope ('this account can see'). It also details the output content (own and shared pages, access levels, monitor counts), making its purpose unmistakable and distinct from sibling tools like list_monitors or get_monitor.

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 provides clear context for when to use the tool: to see all pages accessible to the account, including ownership and sharing details. While it doesn't explicitly exclude alternatives or name when not to use it, the absence of a similar listing tool among siblings makes the intended use obvious.

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