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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds real behavioral value on top: page size (50), the limit ceiling (200) and offset-based continuation, plus what the payload contains (titles and URLs). It stops short of describing result ordering or empty-result behavior.

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 sentences ordered as content → pagination → when-to-use, with no filler. The pagination constraints are front-loaded in the middle sentence where an agent will look for them.

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, the description accepts the burden of describing the return shape and does so ('タイトルと URL'), and pagination is fully explained. Missing only secondary details such as ordering or whether a total count is available, which are minor for a list tool whose annotations already cover safety.

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 semantics itself, and it does: limit's default of 50 and maximum of 200, and offset as the continuation cursor. Only the minimum bound (1) and the offset step size are left to the schema, so the compensation is substantial but not exhaustive.

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 ('読み込んだページの一覧を、タイトルと URL で返します') and pins the scope to one domain (online.instantgakushu.jp), including the returned fields. It distinguishes itself implicitly from the search siblings ('探しても見つからないときに使います') but never names search_pages, get_page or site_overview, so an agent must infer the boundary.

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 two concrete trigger conditions: browsing what pages exist, and falling back when a search finds nothing. That is clear contextual guidance with no exclusions stated and no sibling named, which keeps it just below the top mark.

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