d1_query

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

无 annotations，描述承担全部披露责任，明确说明只读、仅 SELECT、防止误写、默认数据库来源等关键行为，但未提认证或错误处理等细节。

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?

单句描述，先核心功能，再安全性和实现说明，再默认配置，信息密度高且无冗余，结构清晰。

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?

对于两个参数、无输出 schema 的简单工具，描述已覆盖核心用途和默认值，但缺少返回格式说明，略有不足。

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 覆盖率为 100%，描述只是重复了 sql 是 SELECT 查询和 database 默认值，没有增加超出 schema 的语义，因此按基线评 3 分。

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?

描述明确说明“对 D1 数据库执行只读 SQL（仅 SELECT）”，动词+资源+限定条件清晰，与 read_file、execute_command 等兄弟工具区分明显。

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?

明确表明用于只读 SQL 查询，并强调“纯 REST，无需 wrangler/jq”，隐含了使用场景，但没有明确列出“何时不用”或替代工具名称，因此扣一分。

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