list_database_virtual_schema_tables

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

With no annotations, the description must disclose behavioral traits. It states 'list all virtual tables' but the parameter restricts to one database, which is not mentioned. Side effects, read-only nature, and return format are absent, and the scope inaccuracy undermines transparency.

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 sentence and concise, but the inaccuracy (scope mismatch) detracts from structural quality. It is not optimally front-loaded with the most critical constraint (the required virtual_db).

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?

The description does not mention the required virtual_db input, return format, pagination, or what constitutes a virtual table. Given no output schema, the description should cover these aspects but fails to do so, leaving significant gaps for an 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?

The input schema already provides a description for the 'virtual_db' parameter ('The virtual database ID to list datasets for'). The tool description adds no additional meaning. Schema description coverage is effectively 100% (as seen in the provided schema), so baseline is 3.

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 it lists virtual tables (saved questions), but inaccurately claims it does so 'across all databases', contradicting the required parameter 'virtual_db' which filters by a single database. The verb and resource are clear, but the scope is misleading, reducing clarity.

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 on when to use this tool versus siblings like 'list_database_virtual_tables' or 'list_all_tables'. The description lacks context for selection, leaving the agent to infer usage from the name alone.

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