akb_alter_table

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

No annotations are provided, and the description only mentions 'Requires admin role' as a behavioral constraint. It does not disclose potential side effects like data loss from dropping/renaming columns, whether the operation is reversible, or any locking behavior. The description is insufficient for a mutation tool.

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 two sentences, front-loaded with the core purpose, and includes a critical prerequisite. It is efficient with no redundant information, though the second sentence could be integrated for tighter flow.

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?

With 4 parameters including nested objects, no output schema, and the need to convey the ALTER TABLE DDL context, the description is adequate but lacks guidance on return values or potential data impacts. It covers all operations but misses completeness for a complex schema-modification 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 100%, and the description echoes the parameters (add, remove, rename columns) but does not add meaning beyond what the schema's descriptions provide. The grouping of operations is clear, but no additional syntax or format details are given.

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 states 'Modify a table's schema — add, remove, or rename columns via ALTER TABLE DDL', which clearly identifies the action (modify schema) and specific operations (add, remove, rename). It readily distinguishes from sibling tools like akb_create_table and akb_drop_table.

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 implies usage for schema modifications but does not explicitly state when to use this tool versus alternatives, such as when to use akb_update or akb_sql. No exclusion criteria or context are provided, leaving guidance to inference.

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