business_directory_batch_upsert

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

With no annotations and a description that only repeats the name, there is zero disclosure of behavior. The agent has no idea whether this is a write operation, whether it replaces or merges data, what side effects occur, or what the return value is.

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 short, but this is under-specification rather than effective conciseness. It lacks any structure or front-loaded information; every sentence (one sentence) fails to earn its place because it adds no value.

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 8 parameters, a nested context object, 0% schema coverage, and no output schema, this description is wholly incomplete. An agent cannot determine how to structure the call, what the required fields mean, or what to expect in response.

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%, so the description must explain what scopes, domains, concepts, and context mean, but it says nothing. The parameters are completely unexplained, making it impossible to know what values are valid or how they relate to a business directory.

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 directory batch upsert' merely restates the tool name without specifying what entities are being upserted (scopes, domains, concepts?) or what 'batch upsert' actually does. It is a tautology that provides no operational clarity.

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 given on when to use this tool versus siblings like business_contexts_batch_upsert or edge_batch_upsert. The description contains no context, prerequisites, or exclusions, leaving an agent without any basis to choose it.

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