apidog_delete_endpoint

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

No annotations are provided, so the description carries the full burden. It discloses the indirect export-modify-validate-import workflow and the mandatory confirmDelete=true, which adds some context. However, it fails to mention permanent deletion, side effects on related resources, or failure behavior. Score 3 for partial transparency.

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 two short sentences, both informative. It front-loads the action and then states a key requirement. No fluff or repetition. Score 5 for concise structure that earns its 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?

With 13 parameters, nested objects, low schema coverage, and no annotations or output schema, this description is grossly incomplete. It provides only the basic action and one parameter, leaving the agent without enough context for safe invocation. Score 1 for inadequate completeness.

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 23%, and the description adds minimal parameter insight. It only reiterates the confirmDelete requirement, which is already specified in the schema as a const true field. Other parameters like path, method, options, and deleteUnmatchedResources remain largely undocumented. Score 2 for failing to compensate for low 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 tool deletes an endpoint, using a specific verb and resource. It doesn't distinguish from sibling tools like update_endpoint or delete_api_detail, but the resource (endpoint) is distinct enough. Score 4 for clear purpose without sibling differentiation.

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 on when to use this tool versus alternatives like update_endpoint or upsert_endpoint. The only usage hint is the confirmDelete requirement, which is a prerequisite, not a usage context. Score 2 for lack of guidance.

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