database_db_schema

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

With no annotations, the description must disclose behavioral traits. It only states the action without mentioning potential errors (e.g., table not found), permissions required, or whether the operation is read-only. The single sentence provides minimal 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, no redundant words. It is front-loaded with the domain tag and clearly states the purpose. While brief, it is appropriately sized for a simple tool, though some might argue it could be slightly expanded for clarity.

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 has one required parameter, no enums, and an output schema (so return values need not be described), the description is adequate but lacks any usage guidance or behavioral context. It is minimally complete but leaves gaps in transparency and usage.

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 description coverage is 0%, so the description must add meaning. It implies the 'table' parameter is the table name, which provides basic context but no format or constraints beyond the schema's string type. The parameter's role is inferred, but additional details (e.g., required format) are missing.

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 retrieves the CREATE TABLE statement for a specific table, identifying the action ('Get'), resource ('CREATE TABLE statement'), and target ('a specific table'). This distinguishes it from siblings like database_db_tables (list tables) and database_db_query (run arbitrary queries).

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 alternatives such as database_db_tables (for listing tables) or database_db_query (for querying information_schema). The description lacks context on appropriate use cases or exclusions.

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