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

Annotations already declare readOnly, non-destructive and closed-world. The description adds useful behavior beyond that: returns title+URL pairs, paginates 50 at a time, and continuation is via offset. It does not state ordering or what happens past the last page, hence not a 5.

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 sentences, front-loaded with what is returned and the pagination contract, then the usage cue. No filler and nothing repeated from structured fields.

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 read-only list tool with no output schema, the definition covers return content, page size, cap and continuation. Ordering and end-of-list behavior are unstated, which is a minor gap but not one an agent needs to call it 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?

Schema description coverage is 0%, so the description must carry the burden, and it does explain both parameters: 'limit で最大 200 件' and '続きは offset で取れます'. It does not restate types or the minimum bounds, but the semantics of each parameter are conveyed, compensating for the empty schema descriptions.

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 で返します') plus the concrete site scope (instant.aigakushu.online). An agent can tell this is a paginated listing tool, but it never explicitly distinguishes itself from sibling listing/search tools like search_pages or site_overview.

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 situational guidance: use it when you want to know what pages exist, or when a search fails to find something ('探しても見つからないときに使います'). No alternatives are named by name, but the fallback-after-failed-search condition is meaningful routing context.

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