create_mod_project

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

No annotations are provided, so the description must explain behavior. It only says 'Create a C# Muse Dash mod' without disclosing side effects, required permissions, or what files/directories are produced. This leaves the agent unaware of potential overwrites or project structure.

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 concise sentence with no unnecessary words. It is front-loaded with the main action and resource.

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 7 parameters, no annotations, and only a one-sentence description, the tool is underspecified. There is no information about return values, parameter relationships, or usage context, despite an output schema being present.

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 description does not mention any of the 7 parameters. The schema provides types and defaults, but ambiguous fields like 'setting' and 'useful_libs' remain unexplained, and the description adds no semantic context for them.

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 'Create' with a clear resource ('C# Muse Dash mod') and indicates the method ('using MuseDash.Mod.Template'). It clearly differs from sibling tools like build_mod and deploy_mod which imply compilation and deployment.

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 no explicit guidance on when to use this tool versus alternatives. The verb 'Create' suggests it is for new projects, but there is no mention of exclusions or comparisons to sibling tools such as build_mod or deploy_mod.

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