describe_sql_insight_statistic

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

Annotations provide 'readOnlyHint=true', which is consistent with the description's 'Query' nature. The description adds the return format (CSV) but lacks details on error handling, rate limits, or behavioral traits like data freshness or date range restrictions.

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 concise, front-loading the purpose and providing parameter details in a docstring-like format. No redundant sentences; however, the 'Args:' style is slightly informal for a JSON-based environment.

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 tool's simplicity (3 required string parameters, read-only, CSV output), the description provides sufficient context. The output schema exists to detail return fields, so the description need not elaborate. It covers purpose and parameters adequately.

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?

With 0% schema description coverage, the description compensates well by explaining 'dbinstance_id' as the RDS instance ID and providing format examples for 'start_time' and 'end_time' (e.g., '2025-06-06 20:00:00'). This adds meaning beyond the schema's titles.

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 queries SQL log statistics including cost time, execution times, and account, using the verb 'Query'. While it distinguishes itself from siblings like 'describe_db_instance_performance' and 'describe_slow_log_records' by focusing on 'SQL insight statistic', it could be more explicit about how it differs.

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?

No guidance on when to use this tool versus alternatives like 'describe_slow_log_records' or 'query_sql'. The description does not mention prerequisites, constraints, or when not to use it, lacking explicit usage context.

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