icp_controller_check

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

No annotations are provided, so the description carries the full burden. The verb 'check' implies a read-only operation, but this is not explicitly stated, nor are return values or authentication requirements disclosed. The phrase 'Essential before any management operation' adds context about its role but not about its behavior beyond the name.

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 only two short sentences. The first sentence front-loads the primary purpose, and the second adds essential usage context. There is no redundant information, making it highly concise and well-structured.

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 a single parameter and no output schema. The description covers purpose and usage context but does not explain the return value or any prerequisites (e.g., being logged in). Given the low complexity, it is mostly adequate but leaves room for improvement in describing 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 schema already describes the only parameter, canister_id, as 'The canister ID to check' with 100% coverage. The description does not add any additional meaning for the parameter, so the baseline score 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 function: 'Check if you are a controller of a canister.' It uses a specific verb and resource, and the additional context 'Essential before any management operation' further clarifies its role and distinguishes it from sibling tools like icp_manage_canister or icp_get_canister_status.

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 explicitly says when to use the tool: 'Essential before any management operation.' This provides a clear usage context. However, it does not mention when not to use it or suggest alternative tools, so it falls short of a 5.

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