mdk-manage

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

Annotations provide destructiveHint=true (can destroy), idempotentHint=true (safe to retry), and openWorldHint=true (side effects). The description adds the list of operations but does not disclose specific behavioral traits like what gets destroyed or auth requirements. It does not contradict annotations, so it provides some additional context beyond annotations.

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 that effectively summarizes the tool's capabilities, front-loading the key purpose. It is concise, though it could be slightly improved by listing operations in a clearer format (e.g., bullet list).

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?

The description covers the main operations but lacks context such as prerequisites (e.g., existing project), output details, or common use cases. Given the tool's complexity and absence of an output schema, the description is minimally adequate but leaves gaps.

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 coverage is 100% with descriptions for each parameter. The description adds a summary of operations in the tool-level text, but the enum descriptions in the schema already explain each operation. No new parameter-level meaning is added beyond the schema, so baseline score of 3 is appropriate.

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 handles multiple specific operations (build, deploy, validate, migrate, show QR code, mobile app editor), making its purpose unambiguous. It distinguishes from siblings like mdk-create (creation) and mdk-docs (documentation) by focusing on management actions.

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 does not explicitly state when to use this tool versus its siblings (mdk-create, mdk-docs, mdk-gen). While the operations list implies management tasks, no direct differentiation or context for choosing this tool over alternatives is provided.

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