db_list_schemas

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the operation is read-only, has side effects, or depends on authentication/profile state. The read-only nature of a list operation is implied but not stated.

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 extremely concise, using two short clauses to convey purpose and parameter scope. Every word adds value, and it avoids unnecessary detail or repetition.

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's simplicity and absence of an output schema, the description is sufficiently complete for an agent to invoke it correctly. It could mention error conditions or default behavior more explicitly, but the context from sibling tools and parameter descriptions fills most gaps.

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 schema already provides detailed descriptions for both parameters, including profile credential specifics and sticky-session behavior. The description adds a minor hint about the dev|qa override, slightly reinforcing but not significantly expanding on the schema information.

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 action ('List') and the target resource ('non-system schemas'). It distinguishes from sibling tools by focusing on schemas rather than databases or tables, and the optional override notes provide additional scoping.

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 explains when to use the tool (to list schemas) and includes parameter guidance (optional database/profile override). It does not explicitly mention when not to use it, but the sibling tool names implicitly cover alternative listing operations.

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