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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds return fields (title and URL) and route semantics, but it does not disclose pagination, ordering, or whether the list is exhaustive.

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 main function is front-loaded in a single sentence, followed by a compact enumeration of routes. The route list is somewhat long but earns its place by telling the agent what pages exist.

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 simple read-only list tool with no output schema, the description states the return fields (title and URL) and gives useful context about the site structure. It does not describe the exact JSON shape or pagination behavior, but the schema covers limit/offset defaults.

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 needed to explain limit and offset, but it does not mention either parameter. The schema provides only default/min/max constraints, leaving the pagination semantics undocumented.

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 that the tool returns a list of pages loaded into Zippa, including titles and URLs, and enumerates the main site routes. This is specific enough to distinguish it from fetch/get_page, though it does not explicitly contrast with 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?

The title 'どんなページがあるか見る' (see what pages exist) implies a browsing use case, and the description explains what is returned. However, it gives no explicit guidance on when to choose list_pages over search_pages or site_overview, and no exclusion criteria are provided.

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