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

No annotations are provided, so the description must carry the full behavioral burden. It describes the data returned but does not state whether the operation is read-only, whether it requires authentication, whether it has side effects, or how the list is sourced/updated. For a tool with zero annotation coverage, this is a significant gap.

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?

A single, dense sentence that efficiently communicates the tool's data content without filler. It is front-loaded with the resource name and then lists key attributes.

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 the absence of annotations, output schema, and schema descriptions, the description should do more to explain the sole enum parameter and usage context. It partially covers return data but leaves key gaps for an agent to invoke 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?

The schema has one enum parameter ('type') with five values and 0% description coverage, but the description never mentions the parameter or explains what the enum values mean. The description does not compensate for the missing 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?

Description is a noun phrase that names the resource ('AI 與搜尋引擎爬蟲 User-Agent 名單') and enumerates the fields it includes (業者、用途、robots.txt 合規、官方 IP 清單). It clearly states the tool's output content but does not distinguish it from siblings like check_site_crawlers or verify_crawler_ip.

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?

No when-to-use or when-not-to-use guidance. The description only lists the contents; it does not mention alternatives or the context in which an agent should call this tool instead of siblings.

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