update_data

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

With no annotations provided, the description must itself disclose behavioral traits. It only says 'Update data', omitting any details about permissions, side effects, error behavior, or whether it's an upsert. No transparency.

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 short (5 words), but this is under-specification rather than efficient conciseness. It lacks necessary details and is not front-loaded with key info. More substance is needed.

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 has 3 parameters, no output schema, and no annotations, the description is insufficient to allow an agent to correctly invoke it. It misses critical details about required parameters and usage constraints.

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 description coverage is 0%, so the tool description must explain the three parameters (table_name, data, condition). The description does not explain what 'data' or 'condition' mean, nor their expected format. Fails to add value beyond property names.

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 states the tool updates data in a table, which is a clear verb-resource pair. However, it doesn't differentiate from sibling tools like insert_data or execute_sql, and 'Table' is vague. Minimal but adequate for basic 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?

No guidance on when to use this tool versus alternatives. No context about prerequisites, use cases, or when not to use it. Completely missing.

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