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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination via cursor, the 50-item limit, default filtering, or what a 'handle' is. For a list tool with zero annotation gaps, the description contributes no behavioral context.

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?

A single short sentence that is front-loaded and free of filler. But its brevity comes from under-specification rather than efficiency — there is room for one or two more sentences that would materially help.

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 9 parameters, four enums, no output schema and no parameter documentation, the description should at minimum explain filtering and cursor pagination. It says none of that, so an agent cannot confidently construct a call from the definition.

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 0% across 9 parameters, including four enums (group, source, status, seo_state) whose allowed values have no explained meaning. The description compensates for none of this — it mentions no parameter, no filtering semantics, and no pagination model, leaving the agent to guess.

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?

It names a specific verb and resource ('Read page handles'), but 'handles' understates what the tool actually is: a filtered, cursor-paginated page list with 9 parameters. It gives no differentiation from siblings such as pages_seo_get or builds_list, so the agent must open the schema to learn the real scope.

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?

'for builds_open edit_pages' implies the downstream use case (fetch handles to feed an edit/open flow), which is genuine implied guidance. There are no explicit when-not conditions and no mention of alternatives, so routing between this and pages_seo_get is left to inference.

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