Identify address

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds valuable context: it returns a type classification with a contextual summary (balance + SuiNS for wallets, module list for packages, stake info for validators). This goes beyond the annotations and helps the agent understand what to expect.

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 concise and front-loaded with the most important information ('Recommended first step'). It uses a clear structure: purpose, return value, and usage guidance. Every sentence earns its place.

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?

For a read-only classification tool with 2 parameters and full schema coverage, the description is quite complete. It explains the return value and how to use it. The only minor gap is that it doesn't explicitly state what happens if the address is invalid or not found, but that's a minor issue given the openWorldHint annotation.

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 both parameters. The description doesn't add much beyond what the schema provides, but it does imply the address parameter is the main input. Baseline 3 is appropriate when 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 clearly states the tool's purpose: to identify what a Sui address is (wallet, package, validator, or object). It uses a specific verb ('Identify') and resource ('Sui address'), and distinguishes itself from siblings by being the recommended first step before deciding which other tools to call.

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 to use this tool before deciding which other tools to call, positioning it as a triage step. It also lists the categories it can classify, which helps an agent know when it's appropriate. It doesn't explicitly name alternatives, but the context of being a first step is strong guidance.

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