upsert_star_systems_batch

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

With no annotations supplied, the description carries the full behavioral burden and omits the critical upsert semantics: what key determines an existing match (likely name within the structure), whether supplied themes/description overwrite or merge with existing values, and how partial failures or ordering are handled. For a mutation tool this is a significant disclosure gap.

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 sentence with no wasted words, front-loading the operation type and resource. It is efficient but extremely terse given the destructive potential of an upsert.

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 mutation with no annotations and no output schema, the description should explain the upsert matching rule, overwrite-vs-merge behavior, and what the response contains. None of that is present, leaving an agent unable to predict the effect of a call on existing records.

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 100%, so the schema already documents both parameters and the nested item fields, giving a baseline of 3. The description adds only that the operation is scoped to one cosmic structure, which mildly clarifies cosmic_structure_id but does not explain matching keys or item-level semantics.

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 a specific verb pair (insert or update, i.e. upsert) and resource (star systems), plus the batch scope and the parent entity it is scoped to. This distinguishes it from single-record siblings like create_star_system and update_star_system, though no sibling is named explicitly.

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 explicit when-to-use guidance: nothing says when to prefer this batch upsert over create_star_system/update_star_system, nor whether it is safe to rerun for idempotency. The 'batch' and 'scoped to a specific cosmic structure' wording only implies usage context.

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