list_tables

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

Annotations mark readonly, and description confirms read-only. Description adds behavioral context: reads cache from introspect_connection. No contradictions.

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?

Concise, front-loaded with purpose then details. Each sentence adds value. No fluff.

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?

For a simple tool with one parameter, the description covers purpose, output, usage, and prerequisites. Output schema exists, so return details are supplementary. Complete guidance for an AI agent.

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?

Single parameter 'connection' is well-described in schema (name or id, case-insensitive, list_connections for options). Description doesn't add extra beyond schema, but schema coverage is 100%, so baseline 3 applies.

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?

Clearly states the tool lists cached tables with columns, including specific details returned. Distinguishes from sibling describe_table by noting it's for schema-wide overview vs. one table's relationships.

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?

Explicitly says when to use (schema-wide overview) and when not (use describe_table for one table's foreign keys). Also mentions prerequisite: run introspect_connection first if cache empty.

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