hana_execute_ddl

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

No annotations are provided, so the description carries the full burden. It discloses the destructive nature of DROP/TRUNCATE and the confirmation safety measure. However, it does not discuss other behavioral traits such as required permissions, autocommit behavior, or error handling. The warning is good but incomplete.

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 extremely concise: two sentences and a warning line. It is front-loaded with the main action and uses bullet points for key precautions. Every sentence adds value without redundancy.

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, safety, and parameters. Since there is an output schema (as indicated by context signals), the absence of return value details is acceptable. For a DDL tool, it adequately explains the core behavior, though it could mention post-execution effects like schema changes.

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 input schema has 100% coverage with descriptions for both parameters. The description reinforces the confirm parameter's purpose but does not add significant new meaning beyond what the schema provides. Baseline is 3, and the description matches that.

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 executes DDL statements (CREATE, ALTER, DROP, GRANT) in SAP HANA Cloud. It uses a specific verb ('Ejecuta') and defines the resource ('sentencia DDL'). This distinguishes it from sibling tools like hana_execute_query (which executes queries) and hana_describe_table (which describes tables).

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 requires explicit confirm=True to prevent accidental execution and warns about irreversible DROP/TRUNCATE. This provides clear context for safe usage. However, it does not explicitly mention when to use this tool versus alternatives (e.g., hana_execute_query for queries), but the sibling tool names imply differentiation.

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