testneo_delete_saved_api_test_chain

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

The description explicitly states that the tool deletes a resource (destructive), and highlights the guard requiring write permission and confirmation. This adds behavioral context beyond the schema, though it does not mention possible side effects like cascading deletion.

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?

Two sentences: one for purpose, one for guard and endpoint. No redundant information. Efficient and front-loaded.

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?

The description covers purpose, guard, and endpoint. However, without annotations or output schema, it lacks parameter descriptions and return value information. This is a notable gap for a 4-parameter tool.

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, the description should explain parameters. It only references 'confirm' in the guard but does not describe project_id, chain_id, or idempotency_key. This is a significant gap.

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 ('Delete a saved API test chain by id') and the specific resource. It is distinct from sibling tools like save, list, and run, so the purpose is unambiguous.

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?

The description mentions the guard ('TESTNEO_MCP_ALLOW_WRITE + confirm=true') and the backend endpoint, which implies that write permission and confirmation are required. However, it does not explicitly state when not to use this tool or provide alternatives for deletion.

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