generate_test

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

With no annotations, the description must carry the full behavioral disclosure burden. It states 'comprehensive' and lists assertion types, but gives no information about side effects: whether it writes files, overwrites existing tests, requires an existing component, or outputs code vs. saving it. This lack of behavioral detail is a significant gap for a generation tool.

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, front-loaded sentence that directly communicates the tool's purpose and key capabilities without any filler. Every word contributes to understanding what the tool does, making it a model of conciseness.

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 the tool's complexity (7 params, nested objects, no output schema, no annotations), the description is far too sparse. It does not explain the expected input structure for 'fields', the role of 'modelClass', or what the generated test output looks like. An agent would likely struggle to provide valid arguments for all parameters.

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 only 14% (only componentName described). The description partially maps to auth/validation parameters ('hasAuth', 'hasValidation') and database assertions (via 'modelClass'), but it does not explain the complex 'fields' parameter structure (name, testValue, invalidValue) or clarify the meaning of 'hasEdit'/'hasDelete'. The description does not sufficiently compensate for the low schema coverage.

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 uses a specific verb ('Generate') with a concrete resource ('Pest tests for Livewire components') and adds qualifying details (auth, validation, database assertions). It clearly distinguishes itself from sibling generation tools like generate_policy or generate_enum, which target different artifacts.

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 implicitly establishes when to use the tool: when Pest tests for Livewire components are needed. It clearly states the use case and component type, but does not explicitly mention exclusions or alternatives. Since no other sibling tool generates tests, the context is sufficiently clear for selection.

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