create-record

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

With no annotations, the description carries the burden. It mentions 'auto-bulk switching,' which hints at automatic handling of single vs. array input, but lacks details on side effects, permissions, idempotency, or errors. It adds some value beyond the schema but is insufficient.

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 concise single sentence that front-loads the core purpose. While it could include more detail, it avoids unnecessary words and gets the main point across efficiently.

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?

Given 3 parameters, no output schema, and no annotations, the description is too sparse. It fails to explain return values (e.g., created record IDs), error handling, or behavior differences for single vs. bulk creation. The tool is relatively complex, and the description does not compensate.

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 67%, but the description adds no extra meaning beyond restating the ability to create single or multiple records. It does not clarify the 'options' parameter (allOrNone) or provide formatting hints for 'sobjectType'. Baseline 3 is not justified due to coverage below 80%.

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') and the resources ('single or multiple records'), and hints at a unique feature ('auto-bulk switching'). It effectively distinguishes from sibling tools like update-record, upsert-record, and delete-record by focusing on creation.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., upsert-record for create-or-update). An agent would need to infer from the name that it's for new records only, but explicit context is missing.

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