whistle_mock_create

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

No annotations are present, so the description carries full behavioral disclosure burden. It clearly states two key side effects: automatically generating a Value (storing response data) and a Rule (matching URL), and immediately enabling the rule. This goes beyond a simple 'creates a mock' statement. However, it does not mention potential overwriting behavior, failure modes, or authentication requirements.

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 concise sentence, front-loaded with the main action, and contains no redundant or filler content. Every part adds value: one-click creation, auto-generation of value and rule, and immediate enabling.

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 tool has moderate complexity with 6 parameters and nested objects, and no output schema. The description covers the core behavior but does not explain what is returned (e.g., generated rule/value names), or how the tool behaves if the pattern already exists. Given the lack of annotations and output schema, the description is adequate but not fully complete.

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 100%, so the baseline is 3. The description adds minimal parameter semantics—it implies that 'pattern' is used for URL matching and 'response' is the stored data, but this is already stated in the schema parameter descriptions. No additional parameter meaning is provided.

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?

Description clearly states a specific verb+resource: '一键创建完整 Mock 方案' (one-click create complete Mock solution), and explains it auto-generates a Value and a Rule. This distinguishes it from sibling tools that handle rules or values separately, such as whistle_rule_set and whistle_value_set.

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?

Usage is implied: the description says it creates a complete mock solution in one click, suggesting it should be used when both a value and a rule are needed and immediately enabled. However, it does not explicitly state when not to use it or mention alternative tools like whistle_rule_set or whistle_value_set for granular control.

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