node_semantic_batch_upsert

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

No annotations are provided, so the description must fully disclose behavioral traits (e.g., mutation, idempotency, schema constraints). It provides none, only restating the name. The agent has no idea about side effects, concurrency, or failure modes.

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, not concise value. It contains only five words with zero information content beyond the name. There is no structure or front-loading of constraints.

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 a batch upsert tool with nested objects, multiple metadata fields (idempotency_key, tool_version, etc.), and no output schema, the description is grossly insufficient. An agent would be completely lost on how to construct a valid call.

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?

With 0% schema description coverage and 6 parameters, the description must compensate by explaining parameters like 'context' and 'semantics'. It does not even mention them. The agent cannot infer what 'semantics' items 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 is a verbatim repetition of the tool name ('node semantic batch upsert') with no additional context. It fails to state what the tool does beyond the name itself, and does nothing to distinguish it from siblings like edge_batch_upsert or business_mappings_batch_upsert.

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 the many related batch operations (edge_batch_upsert, business_contexts_batch_upsert, etc.). No conditions, no alternatives, no exclusions are mentioned.

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