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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add operational context — and it does: paging behavior (50 per call, limit up to 200, offset for continuation) and the shape of the returned items (title + URL). It does not discuss total counts or ordering, but that is a minor gap for a simple read tool.

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 short sentences, front-loaded with what the tool returns, then paging mechanics, then use cases. Nothing is redundant or padding.

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 listing tool with no output schema, the description covers the source site, the returned fields, pagination limits and the retrieval pattern needed to call it correctly. What an agent needs to invoke it is present.

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 compensate, and it does: it explains that 50 is the per-call page size, that limit can go up to 200, and that offset is used to fetch the continuation. The wording is not fully explicit about offset's unit (items vs pages), which is the only ambiguity.

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 states a specific verb (list / 一覧を返す) and resource (pages loaded on smart-shouene-ai.com), and specifies what is returned (title and URL). It implicitly distinguishes itself from the search sibling by framing itself as the enumeration/fallback path, so an agent can tell it apart from search_pages without opening either schema.

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?

It gives two concrete use conditions: wanting to know what pages exist, and falling back when a search fails to find something. That is clear when-to-use guidance with an implied alternative. It does not name the sibling tool (search_pages) explicitly or state when-not-to-use, which keeps it just below a 5.

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