icp_build_motoko_canister

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

With no annotations, the description carries the full burden. It discloses the core action and the dfx requirement, but fails to mention side effects like generating build artifacts, overwriting existing files, or whether it affects the canister state. This is a significant gap for a build 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 extremely concise, using only two short sentences. It is front-loaded with the primary purpose, and every word contributes meaning without redundancy.

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 lacks key behavioral context: it doesn't specify the output location, whether it builds all canisters or only the specified one, or what the tool returns. With no output schema, this leaves the agent uncertain about side effects and expected outcomes.

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 input schema already comprehensively describes both parameters (project_path and canister_name) with 100% coverage. The description adds no further parameter-level detail, so the baseline of 3 applies.

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 (compile), the input (Motoko canister project), the output (WASM), and the implementation (dfx). This specific verb+resource+output structure distinguishes it from sibling tools like icp_build_rust_canister.

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 implies usage for Motoko projects but does not explicitly mention when to use this tool versus alternatives such as icp_build_rust_canister. It states the prerequisite of dfx being installed, but no exclusionary conditions or explicit alternative guidance.

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