Generate test fixtures

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

No annotations are provided, so the description must disclose side effects. It describes the output content in detail but fails to clarify whether the tool writes files to the given path or returns the scaffolds as a response. This ambiguity about filesystem modification is a significant omission.

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 information-dense sentence with no filler. It could be slightly better structured to separate the two main outputs, but overall it is concise 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?

For a generation tool with no annotations or output schema, the description should state whether it modifies the target directory, what happens to existing files, and any prerequisites. It only describes the product, not the process, leaving critical operational details unknown.

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 description adds value beyond the schema by explaining how the path is used to derive authData from auth fields and inputData from component input fields, and how the component parameter scopes the generation. This contextualizes the parameters more deeply than the schema alone.

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 defines the tool's output: 'Ready-to-run test scaffolds' with specific components (bundle mock, appTester test skeleton). It distinguishes from sibling tools (inspect, lint, validate) which are analytical, not generative.

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 by the purpose but not explicitly stated. The 'Optionally target one component' hint gives some scoping guidance, but there are no explicit alternatives or when-not-to-use conditions.

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