apidog_add_endpoint

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

With no annotations, the description carries the full burden of disclosing side effects and safety traits. It reveals a multi-step process (export-modify-validate-import), but does not explain whether existing endpoints are overwritten, if validation failures are handled gracefully, or what happens to unmatched resources. This leaves significant ambiguity for a mutating operation.

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, front-loaded sentence with no padding. Every word contributes to the basic purpose, though the hyphenated 'export-modify-validate-import' could be clearer. It is concise, but not overly terse to the point of being meaningless.

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 (12 parameters, nested objects, no output schema, no annotations), the description is grossly insufficient. It provides only a high-level workflow and omits crucial context about parameter purposes, preconditions, side effects, or return values. The agent would need to infer too much.

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 only 25% (3 of 12 parameters have any description), and the tool description offers no parameter-level semantics. It does not explain the meaning or role of required parameters (path, method, operation) or the numerous options (schemaOverwriteBehavior, deleteUnmatchedResources, etc.), failing to compensate for the schema's sparse coverage.

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 clearly states the action ('Add an endpoint') and hints at a specific workflow ('export-modify-validate-import'). However, it does not distinguish this tool from siblings like apidog_upsert_endpoint or apidog_import_openapi, leaving the agent to infer the unique value proposition.

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 explicit guidance on when to use this tool versus alternatives is provided. The terse phrase 'by export-modify-validate-import' implies a round-trip process, but there is no mention of prerequisites, exclusions, or selection criteria, leaving the agent without adequate direction.

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