create_or_update_record

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

The description adds behavioral context beyond annotations by explicitly stating the tool is not idempotent and may create duplicates, which aligns with the idempotentHint=false annotation. Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description provides useful warning about repeated calls.

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 relatively short and front-loaded with important context (WRITE, Custom Objects, endpoint). However, it redundantly states 'Create or update record' and 'Creates a new record' in close proximity, which could be tightened.

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 description covers the basic purpose and idempotency, but lacks explanation of upsert behavior (given the name implies update), how to use the 'id' field, or any examples. With no output schema and a nested object parameter, more detail would be beneficial for agent understanding.

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% with both parameters having descriptions in the schema. The tool description does not add any additional parameter-level guidance or examples, so it meets the baseline but does not exceed it.

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 the action ('Creates a new record') and the resource ('record' for Custom Objects), including the HTTP method and endpoint. However, the name 'create_or_update' implies both operations, but the description only mentions creation, creating a minor contradiction that could confuse an agent.

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 description mentions 'Custom Objects' which helps differentiate from sibling tools for other entities, but it does not explicitly state when to use this tool versus alternatives like 'create_a_new_contact'. No when-not or conditional guidance is provided.

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