Generate Performance Report

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

With no annotations, the description carries full burden. It declares the tool is read-only, which is helpful. However, it does not disclose whether the SQL is executed, permission requirements, or output format. The mention of data sources (EXPLAIN, stats, indexes) adds some transparency but leaves gaps.

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 sentence, which is concise but at the expense of necessary detail. It lacks structure and fails to cover key aspects like parameters or usage context.

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 no output schema and moderate complexity (4 params, diagnostic tool), the description is incomplete. It does not explain what the report contains, how to interpret it, or any limitations. More context is needed for effective use.

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 description coverage is 0%, and the description provides no information about any of the four parameters (sql, params, maxRows, profile). This is a critical gap as the description does not compensate for the missing schema documentation.

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 verb 'Generate', the resource 'performance advisory report', and the sources 'EXPLAIN, table statistics, and index metadata'. It distinguishes itself from sibling tools like ob_explain or ob_get_table_stats by combining multiple data sources into an advisory report.

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 mentions 'read-only', implying safe usage, but does not explicitly state when to use this tool over alternatives (e.g., when to use ob_explain vs this report). No guidelines on prerequisites or exclusions are provided.

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