manage_table_columns

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

No annotations are provided, so the description carries the burden. It describes the behavior for each operation, including defaults for add entries and behavior for reorder (ids not in list keep relative order). However, it does not disclose side effects, error handling, or permission requirements.

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 concise paragraph that efficiently covers all three operations without redundancy. It could be slightly improved with bullet points for readability, but it is well-structured and front-loaded.

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 the tool's complexity (4 parameters, 1 required, no output schema), the description covers input semantics adequately. However, it lacks information about output, error conditions, or success/failure indicators. The absence of annotations also reduces completeness.

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 0% description coverage, so the description must compensate. It significantly adds meaning by detailing the structure of 'add' entries (id, label, columnType with defaults), that 'remove' is a list of ids, and that 'reorder' is a full list. This is well beyond the minimal schema info.

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 that the tool adds, removes, or reorders columns on a TABLE_WIDGET_V2, using specific verbs and a specific resource. This distinguishes it from sibling tools like delete_widgets or update_widgets that operate on widgets as a whole.

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 how each operation works (add, remove, reorder) but does not provide explicit guidance on when to use this tool versus alternatives such as delete_widgets or update_widgets. The usage context is implied but not directly stated.

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