mmp_create

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

With no annotations, the description must disclose behavioral traits. It only states the tool creates a package but does not mention required permissions, side effects, or whether it is destructive. The term 'empty' suggests no initial content, but effects on existing resources are unclear.

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. However, it may be too minimal, lacking structure to highlight key details about parameters or behavior.

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 having an output schema (though not visible) and only 2 parameters, the description is insufficient. It does not explain what an 'empty MMP/1.0 package' is, how to specify file/topic, or what the output represents. The existence of an output schema does not compensate for missing contextual information.

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 0%, and the description fails to explain the two required parameters ('file' and 'topic'). The agent receives no semantic information about these parameters, making correct invocation difficult.

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 it creates an empty MMP/1.0 package, specifying the action and resource. However, it does not differentiate from sibling tools that also deal with MMP packages (e.g., mmp_write, mmp_update), but the verb 'create' distinguishes it from read/update/search operations.

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 provides no guidance on when to use this tool versus alternatives like mmp_write or mmp_update. Without context on prerequisites or typical scenarios, the agent cannot determine appropriate usage.

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