manage_bitable_field

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

With no annotations provided, the description carries the full burden of behavioral transparency. It adds the useful API quirk that `type` is required for update even when only renaming, and labels itself as an official API. However, it does not disclose permissions, deletion consequences, or return/error behavior, leaving significant gaps for a CRUD 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 a single sentence that includes the resource, action list, and a key caveat in parentheses. Every clause contributes useful information without repetition. It is well-structured and easily scannable.

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 tool is a multi-action CRUD API with a nested property object and no output schema. The schema compensates for parameter details, but the description does not explain operational outcomes (e.g., delete irreversibility) or response format. While the type-requirement note provides one behavioral nuance, the overall operational picture is incomplete for an agent to use all actions confidently.

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?

All parameters have detailed descriptions in the schema, so the baseline is met. The description's note about `type` for updates duplicates what the schema already states ('Required for create AND update — Feishu API rejects update without it'), so it adds no new semantics. Thus a score of 3 is appropriate.

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 identifies the tool as managing fields/columns in a Bitable table, listing the four actions (list, create, update, delete). This distinguishes it from sibling tools like manage_bitable_table and manage_bitable_record by targeting the column-level resource. The 'Manage' verb is generic but the action enumeration adds specificity.

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's opening phrase 'Manage fields (columns) inside a Bitable table' provides clear context for when to use the tool. It also includes a specific usage note about Feishu requiring `type` for updates, which guides parameter selection. However, it does not explicitly name alternative tools or provide when-not-to-use guidance, so it falls short of the highest bar.

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