describe_table

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

The description claims the tool performs a read-only operation ('Shows'), but annotations set destructiveHint=true, suggesting mutation. This is a direct contradiction, severely undermining transparency. No additional behavioral context is provided.

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?

The description is a single, concise sentence (14 words) that immediately conveys the tool's purpose. Every word contributes value, 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?

The description partially explains output content (columns, types, keys, relationships) but omits details about return format or behavior. The contradiction with annotations leaves a critical gap, as the tool is marked destructive but described as read-only.

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?

Input schema covers both parameters with clear descriptions, achieving 100% schema description coverage. The description adds no extra meaning 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?

The description clearly states it shows detailed schema information for a specific table, listing columns, types, keys, and relationships. The verb 'Shows' is specific and distinguishes it from sibling tools like list_tables or query_database.

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?

The description implies usage for examining schema but does not explicitly state when to use it vs alternatives, nor does it provide exclusions or context for when not to use it.

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