modrinth_create_project

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

Annotations indicate readOnly=false but description adds critical context: the project is created as a DRAFT, nothing public until submission or requested_status set. This is essential behavioral disclosure beyond the schema, though it could detail whether creation is reversible or requires auth.

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?

Three concise sentences, front-loaded with purpose and key behavior, no fluff. Efficient use of words.

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 the tool's complexity (15 params, 4 enums) and no output schema, the description gives enough context for safe use: draft creation, explicit user request, next steps. Could note more about potential errors, but 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 covers all 15 parameters with descriptions, but the tool description adds the key semantic of the 'requested_status' field (stays draft until review) and clarifies the draft workflow. This supplements the schema without redundancy.

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?

Description clearly states it creates a new Modrinth project, explicitly notes it's a draft, and contrasts with sibling tool modrinth_create_version ('After it exists, publish jars with...'). This distinguishes it from related tools effectively.

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?

Provides explicit guidance: 'only call it when the user explicitly asks to create a new project' and explains draft status process. Names the alternative for publishing versions, offering clear when/why.

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