Create a module

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

The description clarifies the folder nature and root-vs-nested behavior, but it does not disclose potential side effects like duplicate creation or permission requirements. The only annotation is idempotentHint: false, which partially covers non-idempotency, but the description does not elaborate on error conditions or return values.

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 two sentences with no redundant information. It front-loads the primary action and immediately provides the key usage distinction, making it highly efficient and scannable.

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 simple create tool with four well-documented parameters, the description covers the critical behavioral distinction (root vs nested) and the schema handles parameter details. It does not explain return values or failure modes, but given the straightforward nature and the annotation hint about non-idempotency, the information is adequate.

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 all parameters are already documented. The description adds marginal value by explaining parentId's role in context of root vs nested modules, but this is already implied in the schema's property description. Thus, the baseline of 3 is appropriate.

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 Test Design module (folder)' with a specific verb and resource, and it distinguishes this from sibling tools like qtest_update_module and qtest_list_modules. The parentId guidance further clarifies scope.

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 gives clear context on when to omit or supply parentId, distinguishing root creation from nested creation. It does not explicitly name alternatives or say when not to use the tool, but the context is sufficient for a simple create operation.

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