list_dialects

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

No annotations are provided, so the description carries the behavioral burden. It clearly states that the tool returns a JSON array Edition and uses the read-only verb 'list', implying no mutation. It could be more explicit about side effects or external dependencies, but for this simple introspection tool the return behavior is disclosed adequately.

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, efficient sentence that front-loads the action and resource before stating the return format. There is no redundant wording, and every phrase adds useful meaning.

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?

For a parameterless listing tool with an output schema already available, the description is complete. It states exactly what is listed, the scope ('current environment'), and the return format, leaving no essential information missing.

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 tool has zero parameters)Skip, as shown by the empty input schema. The description correctly avoids adding parameter details. A zero-parameter tool gets a baseline score of 4 because there is no parameter semantic burden to satisfy.

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 a specific action ('list') and a clear resource: all SQL dialects supported by the current sqlglot environment. It is distinct from the sibling tools analyze_lineage and validate_sql, which clearly perform different operations.

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 when to use the tool, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. Since the sibling tools are unrelated in purpose, an agent can infer the appropriate context, but explicit routing guidance is absent.

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