list_schemas

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

The word 'List' implies a read-only enumeration, and 'configured data source' provides some dependency context. However, with no annotations provided, the description does not disclose error behavior, permission requirements, or what happens when an invalid source is supplied. It is minimally transparent but not rich.

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, focused sentence with no filler or redundant information. Every word contributes to the tool's purpose.

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?

Although the tool has only one parameter and an output schema exists, the required parameter is under-documented and no connection is made to list_data_sources for discovering valid source values. The description leaves the agent uncertain about how to construct a correct invocation.

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% and the only parameter, 'source', has no schema description. The phrase 'configured data source' hints that source refers to a configured source identifier, but it does not explain what values are valid or how to obtain them. Without param-level documentation in the description, this is a notable gap.

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 uses a specific verb ('List'), a specific resource ('schemas'), and a clear scope ('in a configured data source'). This clearly distinguishes it from sibling tools like list_tables and list_data_sources by naming the exact object being returned.

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 gives no guidance on when to use this tool versus alternatives, nor when not to use it. It does not mention that list_data_sources should be used to discover available sources or that list_tables is for table-level enumeration.

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