akb_alter_table

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

With no annotations, the description carries the burden of behavioral disclosure. It states the operation uses ALTER TABLE DDL and requires admin role, providing some transparency about permissions and DDL execution. However, it does not warn about the destructive nature of dropping/renaming columns or mention the preflight check behavior for unique keys, leaving gaps.

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 a single sentence of 13 words, front-loaded with the verb and object. It is concise and free of unnecessary filler.

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?

This is a complex 8-parameter tool with nested objects, no output schema, and no annotations. The description covers only column modifications, completely omitting the ability to add/drop indexes and unique keys. It also lacks warnings about potential data loss or side effects, making it incomplete for the tool's actual scope.

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%, so the baseline is 3. The description adds minimal value beyond the schema by mentioning column modifications but omitting the index and unique-key parameters, which are well-documented in the schema itself.

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 modifies a table's schema with specific actions (add, remove, rename columns) via ALTER TABLE DDL. This distinguishes it from siblings 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 context is clear: use when modifying an existing table's schema. It also provides a key precondition (requires admin role). It does not explicitly name alternatives or exclusions, but the verb 'alter' implies existing tables, making the usage intent unambiguous.

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