forge_unit_test_create

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

The description only says 'Create a new simulation unit test,' which is obvious from the name. No annotations are provided, so the description fails to disclose side effects, permissions, rate limits, or what happens upon creation.

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 sentence with no fluff, being concise. However, it is very minimal and lacks structure or additional helpful details.

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 10 parameters, including complex nested objects like success_criterions, and no output schema or annotations, the description is severely inadequate. It does not explain return values, required permissions, or behavior of the creation process.

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 schema already documents all parameters. The description adds no additional meaning or examples beyond what's in the schema.

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 states 'Create a new simulation unit test,' specifying a verb and resource. It distinguishes from siblings like forge_unit_test_update and forge_unit_test_set_create.

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 on when to use this tool versus alternatives, such as forge_unit_test_update for modifying existing tests or forge_simulate for running simulations. No exclusions or context provided.

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