Analyze Query

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

No annotations are provided, so the description must carry behavioral transparency. It does not disclose side effects, cost/heaviness of the analysis, required permissions, or which parameter combinations are valid. 'Analyze using query profile' implies read-only analysis but never explicitly states behavior beyond that.

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?

Two sentences, each nominally valuable. However, the first sentence is redundant ('analyze' and 'analyze result') and the second is a pointer rather than an essential part of this tool's own description. It is not bloated, but it could be tightened and front-load the instruction more clearly.

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 tool has three optional parameters, no annotations, and no statement on how they combine, but an output schema exists. The description does not explain expected usage for the parameters or warn about possible non-determinism/dependencies on set_session_db. This is below the minimum an agent needs to correctly construct a call.

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?

Schema coverage is 100%, so parameters are already documented. The description adds only 'query profile' context, not additional meaning like whether sql and uuid are mutually exclusive or how db relates to session defaults. It does not degrade below baseline, but it does not help further.

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 'Analyze a query and get analyze result using query profile', which names a verb and resource but is vague about what 'analyze result' means or whether it returns query metrics/plan. It does not clearly distinguish itself from siblings like read_query or analyze_slow_queries_topn, so it is a minimum-viable clarification.

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?

It gives one hint about using set_session_db for the default database but provides no guidance on when to choose this tool over alternatives, nor does it clarify the relationship between the sql and uuid parameters. The agent is left to infer the intended invocation context.

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