upsert_pantheons_batch

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the important matching rule (case-insensitive on name) that determines insert vs update, but says nothing about duplicate names within one batch, partial-failure/atomicity behavior, required permissions, or what the response contains. For a write tool with zero annotation coverage this leaves substantial gaps.

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 filler; the operation and the matching rule are both front-loaded and every clause carries 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?

The tool is simple (one array parameter, no nested objects, no output schema), and the description covers the operation and matching rule adequately. It is still thin for a mutation with no annotations: return values (counts of inserted vs updated) and batch failure semantics are undocumented.

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?

There is only one parameter and schema coverage is 100%, so the schema already documents the array and its name/description item fields. The description adds real meaning beyond the schema by explaining that 'name' is the matching key and that matching is case-insensitive, which the schema does not state.

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 verb pair ('insert or update') and resource ('pantheons') plus batch scope, so the agent knows this is an upsert over a collection. It does not explicitly contrast with create_pantheon or upsert_gods_batch, but the resource noun alone makes the distinction inferable.

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?

Batch semantics imply 'use this when handling multiple pantheons at once' rather than the single-record create_pantheon, and the case-insensitive name match hints at how updates are detected. However, there is no explicit when-to-use/when-not statement and no guidance on preferring this over the single-record tool or the populate_pantheons sibling.

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