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

Annotations already declare read-only, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: pagination of 50 per call, a limit ceiling of 200, and offset-based continuation, plus the shape of the returned data.

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 compact sentences, front-loaded with what is returned, then pagination mechanics, then usage conditions. The embedded brand name in the first sentence is slightly heavy but serves to identify the target site.

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 two-parameter, zero-required, read-only listing tool with no output schema, the description covers return shape, pagination, and usage context. Little an agent needs to call it correctly is missing.

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%, so the description must carry the load, and it does: it explains the default page size of 50, that limit maxes at 200, and that offset retrieves the continuation. It stops short of stating offset units explicitly, but the semantics are inferable from '続き'.

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 (一覧を返す/list) and resource (pages loaded from the site) plus the returned fields (title and URL), which is more than a restatement of the name. It does not explicitly name which sibling it contrasts with, though the 'when search fails' framing implicitly positions it against search/search_pages.

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?

Gives clear when-to-use conditions: when you want to know what pages exist, or when a search attempt has failed to surface a page. It implies the search-then-list fallback workflow without explicitly naming the alternative tools or stating exclusions.

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