describe_table

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

Description describes a read-only operation ('shows'), but annotations set destructiveHint=true and readOnlyHint=false, which is a direct contradiction. No disclosure of any destructive 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?

Single sentence, 14 words, front-loaded with purpose. Every word adds value; 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?

No output schema, but description covers what is returned (columns, types, keys, relationships). However, the destructiveHint=true is not explained, and source_name parameter could use context about what constitutes a 'database source'.

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%, so baseline is 3. Description adds context about output (columns, types, keys) but doesn't elaborate on parameter usage or constraints beyond 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?

Description clearly states the tool shows schema info for a specific table with columns, types, keys, and relationships. Distinguishes itself from sibling list_tables which lists tables, not schema details.

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?

Description implies use when schema details are needed for one table, but doesn't explicitly state when not to use or mention alternatives like list_tables for a list of tables.

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