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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint), the description adds that the tool 'Never executes', which clarifies it only generates statements without running them. It also mentions it 'Respects types, constraints, and FK relationships', adding behavioral detail not implied by annotations. Significant added context.

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 very concise, using only two sentences plus a tier tag, with no wasted words. It front-loads the core purpose ('Generate realistic, schema-aware INSERT statements'), then adds key behavioral constraints. Every clause adds value.

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 that an output schema exists and annotations provide safety hints, the description is complete enough. It explains the tool's role in development/testing, its non-executing nature, and schema awareness. It doesn't need to explain return values because the output schema exists. Minor gaps exist around parameter selection, but these are covered by the detailed schema descriptions.

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 100%, and every parameter has a detailed description, including a comprehensive explanation for the 'connection' parameter. The tool description adds no parameter-specific information, so it doesn't exceed the baseline of 3. It fully relies on the schema, which is sufficient.

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 generates INSERT statements, with a specific verb ('Generate') and resource ('schema-aware INSERT statements'). It distinguishes itself from sibling query tools by adding 'Never executes' and by focusing on development/testing. This is a specific and unambiguous purpose.

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 gives clear context for when to use the tool ('for development and testing') and emphasizes safety ('Never executes'). However, it does not explicitly name alternative tools or state when not to use it. The context is clear but lacks explicit exclusions.

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