nws_upsert_rows

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

With no annotations, the description carries the full burden. It discloses the dual insert/update behavior and the prerequisite read step, which is genuine value, but says nothing about permissions/auth, whether updates are partial or full replacement, conflict handling, or what is returned. Adequate but materially incomplete for a mutation 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?

Three short sentences, no filler, with the core insert/update rule front-loaded before the prerequisite hint. 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?

For a two-parameter but deeply nested mutation tool with no annotations and no output schema, the description covers the mode switch and property-id source but omits how cells/values should be shaped and what sort_order or linked_task_id do. Enough to orient, not enough to call confidently without inspecting the schema.

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 description must compensate. It explains row_id semantics (duplicated from the schema field description) and points to the database for property_id values, but leaves databaseId, cells, value, sort_order, and linked_task_id unexplained. Most of the nested cell structure an agent must construct is undocumented.

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?

States a specific compound verb (create or update) and resource (NWS database rows), which is exactly what an upsert does. The insert-vs-update rule is stated inline, so the agent can distinguish this from nws_read_database and nws_summarize_database without opening the schema.

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?

Gives an explicit conditional for the two modes (omit row_id to insert, set it to update) and a prerequisite workflow hint (read the database first for property ids). It does not name an alternative tool or state when not to use this, but the branching guidance is clear and actionable.

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