mochi_create_deck

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Create,' which implies mutation, but fails to disclose what happens if a deck with the same name exists, required permissions, any side effects, or what response is returned. This is insufficient for a mutation tool.

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 sentence, which is efficient and front-loaded. However, it is arguably too concise given the lack of detail in other dimensions. It earns a 4 for being concise but not sacrificing clarity entirely.

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 complexity of the tool (2 parameters, no output schema, no annotations), the description is minimal but covers the primary purpose. It does not mention nesting via parent_id or any return value, which could be important for an agent. It is adequate but not complete.

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 schema already provides descriptions for both parameters (name and parent_id), achieving 100% coverage. The description adds no extra meaning beyond the schema, so it meets the baseline of 3. No additional semantic value is provided.

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 action (Create) and the resource (a new Mochi deck), which is specific and distinct from sibling tools like mochi_list_decks and mochi_create_card. However, it does not provide any additional context beyond the name, making it only slightly above a tautology.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., mochi_list_decks to check existing decks, or mochi_update_card for modifying a deck). There are no prerequisites or context about when creation is appropriate.

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