list_schemas

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It simply restates the tool's name in a sentence, adding no details about side effects, permissions, error handling, or safety characteristics beyond the implicit read-only nature of 'list'.

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 short sentence that is easily parsed, but it is under-specified. While concise, it omits necessary parameter context, making it insufficiently informative for an agent to fully utilize the tool.

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 an output schema exists, the tool has one optional parameter that is completely unexplained, and there are no annotations. For a tool with low complexity, the description fails to provide the context needed for correct invocation, especially regarding the 'database' parameter.

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 has one optional parameter 'database' with 0% description coverage, and the description makes no mention of it. The agent receives no guidance on how to use the parameter, its meaning, or the effect of the default null value.

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 the specific verb 'List' and identifies the resource as 'available database schemas', clearly distinguishing this tool from siblings like list_tables and describe_table. It precisely states what the tool does without ambiguity.

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 implies usage for enumerating schemas but does not explicitly state when to use it versus alternatives or mention any exclusions. Context is minimal, relying on the obvious purpose.

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