fmod_system_require

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

The description lacks details on permissions, side effects, or error behavior. The inconsistency between the mentioned 'fileName' parameter and the empty input schema undermines transparency.

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 brief but includes an incomplete example ('For example:'). It could be improved by removing the misleading parameter reference and completing the example.

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?

Despite no output schema, the description mentions the return type. However, the missing parameter definition and lack of behavioral context make it incomplete for a tool that loads external files.

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 no parameters (100% coverage), yet the description references a 'fileName' parameter that does not exist. This misleads the AI agent.

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 the tool loads a JavaScript file as a library and returns the module object or null. However, it mentions a 'fileName' parameter despite the input schema having no properties, which introduces confusion.

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. There is no mention of prerequisites, conditions, or exclusions.

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