sct_generate_tests

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

There are no annotations and the description discloses nothing about side effects, prerequisites, overwriting behavior, required project setup, or whether the API key is needed for external calls. For a generative tool that writes files, this lack of behavioral disclosure is a meaningful gap.

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 one short, efficient sentence with no filler. However, it is concise at the expense of substance — some additional context could easily be added without bloating it.

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?

With no output schema and minimal annotations, the description must carry the full context, but it does not explain the required directory structure, whether api_key is required for certain actions, what framework or toolchain is assumed, what files will be produced, or whether existing tests are replaced. This is insufficient for reliable invocation.

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 only 'directory' ('Project directory') while 'api_key' has no description, giving 50% coverage. The description does not compensate by explaining what directory should contain, what the api_key is for, or how the parameters relate to test generation. The agent is left without enough meaning for the undocumented parameter.

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') and a clear resource ('smart contract test suite'), so an agent can tell this tool is meant to create tests rather than, say, a migration or a dashboard. It does not explicitly contrast with sibling tools like sct_add_fuzzing or sct_add_coverage, but the verb 'generate' implies initial creation while the siblings use 'add'.

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 about when to use this tool versus alternatives such as hardhat_add_tests, test_geneate_unit, sct_add_fuzzing, or sct_add_coverage. The description leaves it to the agent to infer that this is about smart-contract test generation, with no exclusions or recommended selection conditions.

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