business_contexts_batch_upsert

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It merely states 'batch upsert', implying mutation, but gives no information about side effects, idempotency, error handling, rate limits, or whether the operation is reversible. It does not reveal anything about what gets modified or what consequences the agent should expect.

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 short phrase, which is superficially concise, but it is under-specified rather than efficiently informative. It does not front-load any useful context and lacks substance that would help an agent. This is not genuine conciseness but rather an absence of content, so it does not meet the criteria for a well-structured description.

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, no output schema, no annotations), the description is drastically inadequate. It does not explain what 'business contexts' are, what the batch operation does, how the parameters relate, what the response looks like, or any behavioral constraints. An agent has almost no information to correctly invoke or reason about this tool.

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 provides zero explanation of the parameters. The schema shows required fields 'context' and 'contexts' and optional fields like 'request_id' and 'idempotency_key', but the description does not clarify their meaning, formats, or relationships. The description fails to compensate for the lack of schema documentation, leaving agents without essential parameter guidance.

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 'business contexts batch upsert' is essentially a restatement of the tool name with spaces. It identifies the resource (business contexts) and the action (batch upsert), but adds no detail about what an upsert entails or what makes this distinct from sibling batch operations like edge_batch_upsert or business_mappings_batch_upsert. There is no elaboration on the specific behavior, so it provides minimal value beyond the name itself.

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 offers no guidance on when to use this tool versus the many sibling tools (e.g., business_mappings_batch_upsert, node_semantic_batch_upsert). There is no mention of prerequisites, intended use cases, or exclusions. An agent is left without any contextual advice on tool selection, making this dimension completely unaddressed.

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