netlicensing_delete_product_module

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

With no annotations, the description must disclose behavior. It mentions the cascade effect ('Also delete all dependent license templates and licenses'), but does not state other traits such as prerequisites (e.g., module must exist), reversibility, or error conditions like what happens if cascade is false but dependents exist.

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 very concise, using a clear structure (purpose statement followed by parameter definitions). Every sentence is necessary 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?

Given that it is a delete tool with two parameters and an output schema (not shown but exists), the description provides enough context for the core operation and cascade effect. However, it lacks details on return values, error handling, or prerequisites, which would make it complete for a delete operation.

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 input schema has 0% schema description coverage. The description adds value by explaining module_number as 'Module to delete' and force_cascade as 'Also delete all dependent license templates and licenses,' which goes beyond the schema's title and type.

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 'Delete a product module,' using a specific verb and resource, and it distinguishes the tool from siblings that delete other entities (e.g., netlicensing_delete_license, netlicensing_delete_product).

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 explicit guidance on when to use this tool versus alternatives or when to set force_cascade to true. While the purpose is clear from the name, the description does not help an agent decide between this and other delete tools or when cascade is appropriate.

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