base_saveDDL

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

The description states it saves a file to disk, which is a write side effect, but annotations set readOnlyHint=true and idempotentHint=true, creating a contradiction. This undermines trust in the tool's behavior.

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 efficient: one sentence for purpose, one for usage rules, then argument list, then return info. Front-loaded with critical information, no fluff.

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 description covers purpose, arguments, and return format, and distinguishes sibling. However, the annotation contradiction undermines completeness, as the agent cannot trust whether the tool is read-only or not. Without output schema, the return description is adequate but not detailed.

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%, so the description compensates well. It explains each parameter (database_name, table_name with comma-separated bulk, object_type with defaults, output_dir with default) beyond the schema's just type and defaults. However, it could add more detail on acceptable values for object_type.

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 extracts DDL and saves it as a .sql file, distinguishing it from base_tableDDL which only displays DDL. The verb 'save' and resource 'DDL' are specific, and the sibling differentiation is explicit.

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 explicitly says to use this tool when the user wants to export/write/download/persist DDL to a file, and not to display/view DDL (use base_tableDDL instead). It also provides argument details and defaults, giving clear context.

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