icp_add_canister_to_project

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

There are no annotations, so the description carries the full burden for behavioral disclosure. It does not explicitly state that the tool modifies dfx.json, what validation happens (e.g., name conflicts), or whether permissions are required. The one-sentence description only restates the operation without revealing side effects or prerequisites beyond 'existing project'.

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, focused sentence that conveys the essential purpose without redundancy or extraneous details. It is front-loaded and easy to parse.

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?

With no output schema, no annotations, and five parameters, the description is too sparse to be contextually complete. It does not explain how canister_type relates to the required or optional parameters (main vs. source), nor does it cover prerequisites or the side effect on the dfx.json file. A more complete description would at least mention that the tool edits the project configuration.

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 100%, so the schema already documents all five parameters. The description does not add additional meaning beyond the schema—it only introduces the overall action. Per the rubric, this merits a baseline 3 since the schema does the heavy lifting.

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 states a specific verb ('Add') and resource ('a new canister') with a clear target ('existing dfx.json project'). This distinguishes it from siblings like icp_create_project or icp_create_canister by emphasizing the 'existing project' context, making the tool's purpose unambiguous.

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 phrase 'existing dfx.json project' clearly implies the tool is used when a project already exists, distinguishing it from project-creation tools. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full alternatives guidance.

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