timps_sql_optimizer

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

Without annotations, the description must convey side effects and safety. It does not mention whether the tool modifies data, requires special permissions, or has any limitations. It only states what it returns, not potential impacts.

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, concise sentence that clearly and efficiently conveys the tool's purpose and output. It is well-structured with the main action front-loaded.

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?

The description explains the output (optimized rewrite, index recommendations, speedup) and lists supported databases, but does not cover error scenarios or limitations. Still, it provides a clear overview of what the tool does and returns.

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 descriptions for all parameters, and the tool description adds little beyond repeating the supported databases. It does not clarify the expected format or additional context for the parameters.

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 tool's function: analyzing a slow SQL query and returning optimization details such as rewrite, index recommendations, and speedup estimate. It also specifies supported databases, distinguishing it from other tools.

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 query optimization but does not explicitly contrast with alternative tools or provide conditions for use. It is clear but lacks explicit guidance on when to use vs. not use.

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