yapi_delete_mock_case

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'delete' and does not explain irreversibility, required permissions, failure behavior, or whether the operation is scoped to a project. This is especially important for a destructive 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 short sentence that communicates the core operation with no filler. It is front-loaded and easy to parse, though its brevity also contributes to missing contextual information.

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 there are no annotations and no output schema, a simple delete-tool description should still clarify parameter usage and deletion scope. The description is too minimal to fully support correct invocation, especially for identifying the right mock case to delete.

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% and the description adds no parameter-level context. The schema only provides names and types (caseId: number, projectId: number), and the description does not explain what each parameter means, whether projectId is needed, or how caseId identifies the mock expectation.

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 states a specific action ('删除' / delete) and a specific resource ('一条 Mock 期望' / a Mock expectation). The tool name and description clearly distinguish it from sibling tools like yapi_save_mock_case and yapi_list_mock_cases, which perform other operations on the same resource.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention that this is the deletion counterpart to save/list/update operations, nor does it state any preconditions such as needing an existing caseId.

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