apidog_upsert_endpoints

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that the operation is a batch upsert and lists per-entry requirements, but it doesn't explain atomicity, partial failure behavior, overwrite semantics, response format, or how duplicates are resolved. This is adequate but leaves meaningful operational gaps.

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?

Three sentences, no redundancy, front-loaded with the core purpose. The efficiency note and input-requirements sentence each earn their place.

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?

For a batch mutation tool with no annotations and no output schema, the description should ideally describe what the call returns, whether the batch is all-or-nothing, and what identifies an existing endpoint for update. It covers the input contract but leaves those operational consequences unstated.

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 coverage is 100% and the description adds value by specifying that each entry requires method, path, and 'the full operation object,' which clarifies the intended niche of the operation parameter. This goes beyond the schema's bare property names and types.

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 names a specific verb (create or update), a resource (multiple endpoints), and a distinct execution mode (batch in a single import). It explicitly contrasts with apidog_upsert_endpoint, so an agent can immediately distinguish it from the singular sibling.

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?

It states when to prefer this tool: for batch processing of multiples endpoints, and it explicitly notes efficiency over calling apidog_upsert_endpoint multiple times. It doesn't mention exclusions or alternatives like apidog_import_spec, so it stops short of full routing guidance.

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