List SQLite Tables

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The phrase "without loading data" adds a genuine efficiency trait beyond the annotations, but nothing is said about what "user tables" excludes or how large/slow the call might be on big schemas.

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?

Two sentences, zero filler: the capability comes first, the usage cue second. Nothing is repeated from the title or schema.

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 read-only discovery tool with full schema coverage and annotations, the description covers purpose, output shape, and the key non-obvious trait (no data loading). It only lacks the sibling-differentiation that would make selection unambiguous.

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 coverage is 100% – both db_path (with accepted extensions) and include_views (default true) are documented in the schema. The description adds no format, default, or behavioral nuance beyond that, 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?

States a specific verb+resource (list user tables and views in a SQLite database) and adds the return payload (row counts and column counts), so the agent knows exactly what it gets. It does not, however, distinguish itself from siblings like sqlite_describe_table or sqlite_summarize_database, leaving overlap for the agent to resolve.

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?

"Use this to discover database schema without loading data" gives a clear triggering context. There are no explicit exclusions (e.g., 'use sqlite_describe_table for a single table's columns'), so the alternative-routing piece is missing.

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