post-crm-objects-v4-objtype-batch-upsert_upsert

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only notes that a body parameter is required and points to the schema, but fails to mention mutation side effects, idempotency, error behavior, or authentication needs. This is a significant gap for a batch write operation.

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 short and gets to the core purpose quickly. However, the 'REQUIRES body parameter' sentence is somewhat redundant and the all-caps style adds minimal value, so it is not maximally concise.

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 complex batch upsert tool with no output schema and no annotations, the description is too thin. It does not explain return values, the role of idProperty, partial failure behavior, or provide context beyond the schema. An agent would need to infer too much.

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% and each parameter already has a description, so the baseline is 3. The description adds no semantic details beyond what the schema provides and merely redirects to the inputSchema, which does not enhance parameter understanding.

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 clearly states a specific action ('Create or update a batch of objects') and the distinguishing mechanism ('by unique property values'), which sets it apart from sibling batch-create and batch-update tools. This gives an agent enough to recognize an upsert operation.

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?

The phrase 'by unique property values' implies when to use this tool (upsert scenarios), but there is no explicit guidance about when not to use it or which sibling alternative to choose. The description provides implied usage context but lacks clear exclusions or alternative recommendations.

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