business_mappings_batch_upsert

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the operation with no mention of side effects, idempotency (despite an idempotency_key parameter), authorization needs, or data transformation behavior. This is a significant gap for a mutation tool.

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 extremely concise, but it is under-specified rather than efficiently concise. It fails to convey necessary information, resembling the minimal 'Process' example. It is not a balanced single sentence that earns its place; it is a bare restatement.

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 the tool's complexity (6 parameters, nested objects, batch upsert, no output schema) and lack of annotations, the description is utterly inadequate. It leaves the agent without essential details about input structure, behavior, or return values, making correct invocation nearly impossible.

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 0% and the description mentions no parameters explicitly. It adds no meaning to the context, mappings, request_id, tool_version, schema_version, or idempotency_key fields. The agent has no guidance on what the mappings array should contain or how context is structured.

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 states a specific verb ('upsert') and resource ('business mappings'), which gives a basic sense of operation. However, it does not explain what business mappings are or distinguish this batch upsert from siblings like business_directory_batch_upsert or business_contexts_batch_upsert. It adds no meaning beyond the tool name.

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. The description does not mention any context, conditions, or exclude scenarios. With many sibling batch upserts and read/search tools, the agent is left without direction on when to prefer this tool.

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