買取大陸

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds that it returns the full page body and is useful for accuracy checks, but does not describe authentication, rate limits, or other operational 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 short sentences front-load the purpose, then input handling, then the key usage instruction. Every sentence contributes useful context without unnecessary length.

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?

Given a simple one-param read tool with annotations, an output schema, and full parameter coverage, the description supplies enough context about purpose and when to use it. The main gap is that it does not explicitly distinguish itself from sibling read/search tools.

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 100% and the single id parameter is fully documented in the schema. The description repeats that id can be a search-result id/URL or a URL/path, but adds no syntax or format details beyond what the schema already provides.

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 action (返します) and resource (ページの本文), including the target domain. It does not, however, distinguish itself from sibling tools such as get_page or search_pages, so it is clear but lacks sibling differentiation.

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 a clear when-to-use instruction: verify the page body before answering for accuracy-critical items like fees, dates, conditions, and terms. It does not state when not to use it or name alternative tools.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that it is retained for backward compatibility and returns a different shape than fetch, which is useful, but with no output schema it never describes that shape or any size/pagination 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 short sentences, front-loaded with the legacy status and closing with the actionable 'use fetch instead' recommendation. No padding, though the middle sentence about the different return shape is a promise without a payoff.

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 legacy read tool this covers the essential routing, but with no output schema and a statement that the return form differs from fetch, an agent still cannot anticipate what it will receive. The core 'different shape' claim is left unexplained.

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 100% for the single url parameter, and the description adds nothing about the parameter (e.g., accepted URL forms). Baseline 3 applies since the schema carries the semantics.

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 the verb/resource (returns the page body) and explicitly frames itself as the legacy alias of fetch for the site 買取大陸. It distinguishes itself from the sibling fetch by noting the return shape differs, though it never says how it differs, leaving the actual output semantics vague.

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 an explicit routing instruction: use fetch for new usage, keep this only for already-connected clients. That is a clear when/when-not with a named alternative, but it omits any condition under which get_page is still the preferred call.

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

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.

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint=false, destructiveHint=false), and the description adds genuinely new behavior: only indexed/loaded pages are searchable, post-load updates are excluded, and a prescribed anti-hallucination fallback when nothing is found. That is meaningful context beyond the structured fields.

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?

Front-loads what is searched and the trigger for using it, then layers scope limits and the retry/fallback ladder. It is somewhat long, but nearly every sentence adds actionable information about scope or recovery behavior.

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?

Covers scope, freshness limits, retry strategy, and fallback, and an output schema exists so return formatting need not be described. The main gap is that it does not differentiate itself from the equally named sibling search_pages, which is the most likely source of misselection.

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 100% for the single 'query' parameter, so the schema already carries the semantics. The description implies multi-word/searchable terms but adds no syntax, matching, or tokenization details beyond the example already present in the schema.

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 (search) and resource (pages loaded from 買取大陸/kakeruyone.com) and describes the return (excerpt + URL), which is more than the generic name 'search' conveys. However, it never distinguishes this tool from the sibling 'search_pages', which an agent could easily confuse with it.

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 explicit usage context ('買取大陸 について質問されたら、まずこれを使ってください'), clear scope limits, and a concrete retry procedure (rephrase, expand abbreviations, try synonyms) plus a fallback instruction not to guess. It does not, however, state when to prefer fetch/get_page/search_pages instead, so the routing versus siblings is left implicit.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful deprecation context and notes the return format differs from 'search', though it does not specify how the format differs.

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 concise sentences front-load the legacy status and immediately route the agent to the appropriate alternative. No sentence is wasted.

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 deprecated read-only search with annotations covering safety and no output schema, the description provides enough context to avoid misuse. It could mention the limit parameter or the nature of the return-format difference, but these are minor gaps.

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 only 50%; the 'query' parameter is documented in the schema, but 'limit' has no textual description in either schema or description. The description does not mention any parameters, so it fails to compensate for the incomplete schema documentation.

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 and resource ('search inside the site') and explicitly distinguishes this legacy alias from the primary 'search' tool by noting the different return format. It also identifies the site (kakeruyone.com), so an agent can tell what it does without opening the 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 explicit routing guidance: this is kept only for existing connections, and new uses should call 'search' instead. The alternative is named and the condition for using the alternative is clear.

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

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

Annotations already declare readOnly/non-destructive/closed-world, so the safety profile is covered. The description adds valuable return-value context (type, description, page count, main pages) in the absence of an output schema, though it omits operational details like auth or rate limits.

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 is returned, followed by the usage trigger. Every sentence earns its place with no redundancy.

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 zero-param, read-only overview tool with no output schema, the description covers both the purpose and the main fields returned, which is largely sufficient. Minor gaps remain about the exact response shape, but nothing critical for invocation is missing.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly adds nothing misleading about inputs.

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+resource: returns an overview of the '買取大陸' site. It enumerates what the overview contains (type, description, pages loaded, main pages), which distinguishes it from page-level siblings like get_page and list_pages.

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?

Explicitly says to use it when first wanting to grasp the whole site ('最初にサイトの全体像をつかみたいときに使います'), implying it precedes page-level tools. It lacks explicit when-not guidance or named alternatives, but the context is clear.

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