icp_deploy_frontend

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states what the tool does without mentioning side effects (e.g., whether existing files are overwritten), prerequisites, or any destructive potential. There is no additional context beyond the basic action.

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 that front-loads the main verb and resource. It is appropriately sized for a simple tool, though it could include additional guidance without becoming verbose. No wasted words.

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 tool has no annotations or output schema, so the description must compensate. It does not explain prerequisites (e.g., existing asset canister), the effect on existing assets, or what is returned. This makes the description incomplete for an agent deciding how and when to use it.

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 has 100% coverage for both parameters, each with a clear description. The tool description does not add any parameter-specific details beyond the schema. As a result, the baseline score of 3 is appropriate since the schema fully documents the parameters.

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 "Deploy static frontend files to an asset canister" uses a specific verb ('deploy') and clearly identifies the resource ('static frontend files' to 'asset canister'). It distinguishes itself from sibling tools like 'icp_deploy' by specifying static frontend files and the asset canister target.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies its use case via the tool name and action, but does not state exclusions or mention that 'icp_deploy' is for backend canister deployment. The context is clear but lacks explicit guidance.

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