list_tables

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

With no annotations provided, the description carries the full burden. It discloses the list operation, the inclusion of comments, and via the parameter description, the default behavior of returning all non-system schemas when no filter is given. However, it does not mention potential permissions, output ordering, or any limits, leaving some behavioral ambiguity.

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, front-loaded sentence with no wasted words. It efficiently conveys the tool's core function.

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?

Given the tool's low complexity, the presence of an output schema, and the parameter's full documentation in the schema, the description is nearly complete. It could explicitly state that this is a read-only operation, but the word 'List' implies no side effects. Minor gap: no direct statement about system schema exclusion if a specific schema is provided, but the parameter description already covers this.

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?

The input schema provides a complete description for the single optional 'schema' parameter, including examples and default behavior. The tool description itself adds no additional parameter-related meaning, so the baseline of 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?

The description clearly states the tool's function: listing all tables in the database. The addition 'with their comments' specifies the output detail, distinguishing it from sibling tools that describe single tables or sample data.

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 provides no guidance on when to use this tool versus its siblings. It merely states what it does, without mentioning alternatives or exclusions. The parameter description offers some behavior context (filtering by schema) but does not address tool selection.

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