clitest_add_mocks

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

With no annotations, the description must carry the full behavioral burden, but it only says the tool generates mock utilities and is a Pro feature. It does not disclose side effects like files created or modified, whether api_key validation is enforced, or what happens on failure.

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 compact and front-loaded, with the primary action stated immediately. The parenthetical 'Pro feature' is a useful signal and earns its place. The lack of supporting detail prevents it from being an ideal concise description.

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?

For a tool with no annotations and no output schema, this description is too sparse. It leaves unclear what mock utilities are generated, where they are written, whether the api_key is required for the Pro gating, and what the expected outcome is. An agent cannot confidently invoke this tool from the description alone.

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?

The schema documents 'directory' as 'Project directory', but 'api_key' has no description in the schema. The tool description adds no parameter semantics at all, not even clarifying how api_key is used or that directory is the target project. With schema description coverage at 50%, the description should have compensated but does not.

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 ('Generate') and a resource ('CLI mock utilities'), and the 'CLI' qualifier helps distinguish it from generic mock-generation tools. However, 'mock utilities' is somewhat vague, and the description does not explicitly differentiate it from closely related siblings like clitest_generate_suite or clitest_add_snapshots.

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 is provided on when to use this tool versus alternatives such as clitest_generate_suite, clitest_add_snapshots, or test_generate_mocks. The 'Pro feature' note signals licensing but not a usage context, prerequisites, or workflow.

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