ts_update_cell

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

With no annotations, the description carries the full burden. It discloses that the tool is a write operation, disabled by default for safety, and only affects one cell. However, it does not describe error behavior (e.g., what happens if the row or column doesn't exist), side effects, or return values.

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 concise at about 5 sentences, front-loading the purpose and examples, then covering safety and scope. No extraneous information.

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 no output schema, 5 parameters with 0% schema coverage, and being a write tool, the description provides adequate purpose and safety context but lacks parameter details, error handling, and expected output, which are important for safe usage.

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 coverage is 0%, so the description must compensate. It mentions that the row is identified by 'id_column=id_value' and implies the 'column' and 'value' parameters are for the cell. However, it does not explain all five parameters (table, id_column, id_value, column, value) in detail, nor does it list valid tables or value types.

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 verb 'update' and the resource 'single column on a single row in the Target Scheduler database', with specific examples like 'disabling a target or bumping a project's priority'. It also distinguishes from bulk operations by stating 'there's no bulk-edit or delete here on 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 explicitly advises that the tool is disabled by default and requires setting the environment variable TS_ALLOW_WRITES=true, and recommends backing up the database. It also implies that this tool is not for bulk edits or deletes. However, it does not explicitly name alternative tools for those operations.

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