upsert_celestial_bodies_batch

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

With no annotations, the description carries the full burden and does not disclose the critical upsert semantics: what key is used to match existing records (presumably name within a star system), whether unmatched bodies are created, whether omitted fields are cleared or preserved, and whether the batch is atomic on partial failure. It also says nothing about permissions or response behavior.

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?

A single front-loaded sentence with no filler, and the scope constraint appears immediately. It is efficient, though the terseness comes at the cost of the behavioral detail a batch mutation needs.

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 batch write tool with zero annotation coverage and no output schema, the definition is thin: the batch's effect on existing records, the match key, and error behavior are all unstated. The schema covers the input shape, but an agent could not confidently predict the outcome of a call from this description.

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 100%, so both parameters are already documented; the baseline is 3. The phrase "scoped to a specific star system" does add a little meaning by clarifying that star_system_id is the parent scope for the whole batch rather than a per-item field, but no matching or validation semantics are added.

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 names a specific verb pair ("batch insert or update") and a specific resource ("celestial bodies") plus the scope ("scoped to a specific star system"). That distinguishes it from the single-record create_celestial_body/update_celestial_body tools, though it never explicitly contrasts itself with near-name siblings like populate_celestial_bodies_bulk.

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?

There is no when-to-use guidance: nothing says when to pick this over create_celestial_body, update_celestial_body, or populate_celestial_bodies_bulk, nor what distinguishes 'upsert' from 'populate' in this API. The agent must infer the choice from the tool name alone.

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