bulk_create_contacts

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

Annotations already indicate a write operation (readOnlyHint: false) and non-destructive (destructiveHint: false). The description adds no behavioral context, such as whether the bulk creation is atomic, how partial failures are handled, or what the response contains. It merely repeats the implication of the name.

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, front-loaded phrase with no redundant words. It is concise and to the point, though it sacrifices substance for brevity.

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 bulk creation tool with a complex request body array and no output schema, the description is inadequate. It does not explain return values, error behavior, or any constraints that the 'bexio API' body might impose, leaving the agent under-informed.

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?

The input schema has one parameter, 'body', with 100% description coverage ('Request body as defined by the bexio API'). The tool description does not add any further parameter information, so the baseline score of 3 applies.

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 'Bulk create contacts' is essentially a restatement of the tool name with underscores replaced by spaces. It does not add any further information about the operation's scope or differentiate it from sibling tools like create_contact, which presumably creates a single contact.

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?

There is no guidance on when to use this tool versus alternatives such as create_contact, update_contact, or list_contacts. The description does not mention any specific use cases, exclusions, or alternative tools.

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