update_table_fields_order

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

The description implies a mutation (reordering) but lacks details on side effects, required permissions, or whether changes are reversible. With no annotations provided, the description fails to disclose behavioral traits beyond the basic action.

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 (one sentence) but lacks detail to be useful. It is front-loaded, but underspecification reduces its value.

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 lack of annotations, no output schema, and the complexity of having a nested input object, the description is severely incomplete. It does not cover return values, error handling, prerequisites, or any additional context needed for safe invocation.

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 description does not add any meaning beyond the input schema. Although the schema itself includes property descriptions, the tool description makes no mention of parameters, and schema coverage is 0%, so it fails to compensate.

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 action 'Reorder fields in a table' and specifies the product 'Metabase'. It distinguishes from sibling tools like 'update_table' or 'update_field' by focusing specifically on field order reordering.

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?

No guidance is provided on when to use this tool versus alternatives such as 'update_table' or 'update_field'. There is no context about prerequisites or exclusions.

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