webdev_sql_formatter

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

The description mentions formatting actions like indentation and keyword formatting, but lacks details on input requirements, error handling, or side effects. It defers full guidance to describe_tool.

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 relatively concise, but includes an unnecessary 'Menu ID' detail and relies on another tool for full guidance, which adds noise for the agent.

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 open schema and lack of output schema or annotations, the description is incomplete and points to describe_tool for full guidance, indicating insufficient standalone information.

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 input schema is open (additionalProperties: true) with no defined parameters, and the description does not clarify how to provide SQL code for formatting, leaving invocation ambiguous.

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 it is an SQL Formatter that formats, beautifies, and structures SQL code, distinguishing it from sibling formatters for other languages.

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 SQL formatting but does not provide explicit guidance on when to use this tool over alternatives like webdev_code_formatter or webdev_xml_formatter.

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