Collect Query Dump And Profile

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

With no annotations, the description must carry the full behavioral burden. It discloses that output is large and requires special processing, but it does not mention side effects, permissions, resource cost, or what the dump/profile actually contains.

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 short and front-loaded with the main action, but the comma-spliced, ungrammatical phrasing ('it's', 'need special tools') makes it read as a rough note rather than a polished definition. It is compact but awkwardly structured.

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?

For a tool with no annotations and no output schema, the description should explain what a 'query dump and profile' are and how an agent should handle the very large output. It does not, so an agent may not know what to do with the result or how to distinguish this from similar analysis tools.

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 fully describes both parameters ('database' and 'query to execute'), so the description adds limited parameter-level meaning. It only reinforces that the query is executed and that output is large.

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 names a specific action ('Run a query') and the resulting artifacts ('query dump and profile'), so the basic purpose is clear. It does not explicitly differentiate this from siblings like analyze_query, but 'dump and profile' gives enough distinct identity.

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 warning that output is very large and needs special tools implies the tool is intended for raw collection followed by external processing. It does not name alternatives or state when not to use it, leaving the decision partially to inference.

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