manage_bitable_record

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

With no annotations, the description carries the burden of disclosing side effects and constraints. It adds useful context about array support (up to 500 records) and its 'Official API' status, but it does not mention authorization requirements, response formats, or that create/update/delete are mutating operations beyond the action names. The description is partial but not misleading.

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 concise sentences that front-load the official API status and core purpose, then list actions and a key batching detail. No filler or redundancy; every sentence earns its place.

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 (10 parameters, 5 actions, no output schema), the description provides a compact overview but does not explain response structure, pagination nuance, or action-specific parameter usage beyond what the schema already provides. The schema is thorough, so this is a moderate gap rather than a critical omission.

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 schema descriptions cover 100% of parameters, so the baseline is 3. The description adds minimal extra semantic value beyond the schema: it highlights the array acceptance for create/update/delete, but this is already detailed in the 'records' parameter description. Thus, no significant augmentation.

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's function: 'Manage records (rows) inside a Bitable table' with explicit action enumeration ('action=search, get, create, update, delete'). This distinguishes it from sibling tools like manage_bitable_table or manage_bitable_view by specifying the resource as records/rows. The verb 'manage' plus the resource and action list fully clarify the purpose.

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 when to use this tool (for manipulating bitable records) and even outlines the supported operations, but it does not explicitly contrast it with sibling tools or say when not to use it. No alternatives are named, so the agent must infer the usage context from the resource name and the list of actions.

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