describe_table

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

注解已声明readOnlyHint和destructiveHint均为假，描述在此基础上补充了'不读取样本数据'的具体限制，并列出所查看的元数据类型，提供了注解之外的上下文，且无矛盾。

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描述覆盖率为0%。描述未提及table和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?

描述具体指明工具用于查看业务表字段、类型、主外键和索引，并明确不读取样本数据，与query等数据查询工具形成清晰区分。动词'查看'和资源列表具体，能准确传达工具功能。

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?

描述通过'不读取样本数据'暗示了与查询工具的差异，但未明确说明何时应使用本工具而非替代工具（如query或explain），缺乏显式的使用条件或排除指引。

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