peach_create_contacts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Create or upsert' which implies mutation, but doesn't specify permissions required, rate limits, error handling for partial failures, or whether the operation is idempotent. The 'bulk' aspect hints at performance considerations but lacks concrete details.

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 a single, efficient sentence that clearly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'upsert' entails (e.g., merge logic), what happens on conflicts, the response format, or error conditions. Given the complexity of bulk operations and lack of structured safety hints, more behavioral context is needed.

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 the schema fully documents the 'contacts' parameter and its nested properties. The description adds minimal value beyond the schema by implying bulk operations and upsert behavior, but doesn't provide additional syntax, format, or constraint details. This meets the baseline for high schema coverage.

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 ('Create or upsert multiple contacts in bulk') and the resource ('in the Peach account'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'peach_create_contact' (singular), leaving some ambiguity about when to use bulk vs. single operations.

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 provides no guidance on when to use this tool versus alternatives like 'peach_create_contact' (for single contacts) or 'peach_update_contact' (for updates). It mentions 'bulk' but doesn't specify thresholds or scenarios where bulk is preferred over individual operations.

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