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

Annotations already declare this a safe read (readOnly, non-destructive, closed-world). The description adds genuinely useful behavioral detail beyond them: page size of 50, a limit cap of 200, and offset-based continuation. It does not describe ordering or error behavior, so 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?

Three tight sentences with no filler, front-loading what is returned before the pagination mechanics and use cases. Nothing is wasted, though it is slightly dense in a single run-on.

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 two-parameter list tool with no output schema, the description covers return contents (title, URL), pagination, and usage context. Ordering of results and total count are not addressed, a minor gap.

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 parameter meaning, and it does: limit is explained as page size with a 200 maximum, and offset as the continuation cursor. It omits the defaults (50/0) that the schema already declares, which is acceptable.

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 (returns a list of pages with title and URL) and scopes it to the「買取大陸」site. It clearly separates this from search-flavored siblings by implying a find-everything listing, though it does not name a specific sibling tool.

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 when-to-use conditions: wanting to know what pages exist, and having failed to find something by searching. The second condition implicitly routes the agent away from search tools, but no sibling is named explicitly.

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