edge_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. 'Upsert' implies insert/update, but the description does not explain behavior on conflicts, idempotency, validation, or any side effects. Both schema and description are silent on these crucial aspects.

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?

At three words, it is extremely short but this is under-specification, not conciseness. There is no structure, no front-loading of key constraints, and no additional information beyond the name.

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?

This is a complex tool with nested objects, six parameters, and no output schema. Without any description of parameters, behavior, or return values, an agent has virtually no chance of using it correctly. Complete inadequacy for the tool's complexity.

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 compensate by explaining parameters, but it provides none. The required 'context' (with repository_id and target_commit) and 'edges' array are entirely undocumented. An agent cannot determine what data to supply or how to structure it.

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 'edge batch upsert' is little more than a restatement of the tool name. It fails to specify what an 'edge' is, what operation is performed, or what the batch upsert accomplishes. An agent cannot infer the tool's purpose 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?

No guidance is provided on when to use this tool versus its many siblings (e.g., edge_validate, node_semantic_batch_upsert, business_directory_batch_upsert). There is no mention of prerequisites, alternatives, or conditions that should select this tool over others.

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