icp_deployment_guide

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool retrieves a 'guide,' which implies a read-only operation, but it does not explicitly confirm safety, side effects, or what the returned guide contains. This lack of detail leaves the agent uncertain about the tool's behavior.

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 immediately conveys the tool's purpose. It is front-loaded with the key term 'guide' and avoids unnecessary details, earning full marks for efficiency.

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 is minimal but sufficient for a simple, parameter-less tool. It tells the agent that this is a guide on safe deployment practices, but it does not elaborate on the guide's content, format, or how it differs from other informational tools. Given the lack of an output schema, a bit more detail about what the guide includes would improve completeness.

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 tool has zero parameters, and the schema is empty. According to the rubric, a zero-parameter tool receives a baseline of 4. The description does not need to add parameter information since there are none to document.

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 tool's purpose: to get a comprehensive guide on safe deployment practices for ICP canisters. The verb 'Get' and the specific resource 'guide' on 'safe deployment practices' distinguish it from sibling tools like icp_deploy or icp_preflight_check, which perform actions rather than provide information.

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 usage is implied: an agent would use this tool when seeking guidance on safe deployment practices. However, it does not explicitly state when to use it versus alternatives, nor does it mention exclusions or prerequisites. Given the many deployment-related siblings, clearer guidance would be beneficial.

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