base_saveDDL

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

With no annotations, the description carries full burden. It mentions server-side execution and file saving, but does not disclose if the operation is read-only or destructive (e.g., overwrites files), nor any permissions or error 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 well-structured with a purpose sentence, rationale, and argument list. It is relatively concise but could be slightly tighter without losing clarity.

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, the description includes return values (file path, size, metadata) and covers all parameters. Missing details about error handling and edge cases, but overall adequate for a DDL extraction tool.

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 coverage is 0%, so description must compensate. It provides detailed explanations for all 4 parameters, including examples (e.g., 'MKTG_USR', 'SP_LOAD...'), defaults, and object type options, adding significant meaning beyond the schema.

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 'Extracts the complete DDL of a Teradata object and saves it to a .sql file', specifying a specific verb (extracts and saves) and resource (DDL). It distinguishes from sibling tools like base_tableDDL by adding the file saving capability.

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 explains when to use this tool: 'solves the token limit problem' for large DDL content. It implies usage context but does not explicitly mention when not to use or name alternatives like base_tableDDL.

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