list_tables

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

There are no annotations, so the description carries the full burden. The word 'Lista' implies a read-only operation and 'todas' indicates exhaustive coverage, which is useful. However, it does not disclose output shape, whether system tables or views are included, ordering, or failure modes. For a simple list tool this is a moderate gap, not a severe one.

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 clear sentence with no filler. It front-loads the verb and states the target resource completely. Every word earns its place.

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 zero-parameter, low-complexity read tool the description is mostly complete: it names the operation and the database. It would benefit from noting the return format or scope details, but an agent can safely invoke this tool with no arguments based on the description alone.

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 tool has zero parameters, and the schema is empty, so there is nothing for the description to add about parameters. Baseline 4 applies for zero-parameter tools. The reference to the Turso database adds context but is not parameter documentation.

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 states the specific operation ('Lista') and the resource ('todas as tabelas do banco de dados Turso'). This unambiguously identifies the tool as a list operation over the full table set in the Turso database, distinguishing it from sibling tools like describe_table or execute_select.

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?

No guidance is provided about when to use this tool versus alternatives, or when not to use it. The description only states what the tool does, leaving the agent to infer when listing all tables is the right choice among the many sibling tools.

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