t2000_address

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

No annotations, but the description indicates a simple getter with no side effects. It adds value beyond the empty schema, being clear and honest about its 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?

Two short, front-loaded sentences with zero unnecessary words. Every sentence serves a purpose.

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 zero-parameter no-output-schema tool, the description is complete: it explains what it does and provides a useful cross-reference (`t2 fund`).

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?

Zero parameters, so the description cannot add parameter-level detail. Baseline is appropriate; no issues.

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 it gets the agent's Sui wallet address, and distinguishes from siblings by noting it's identical to the first line of `t2 fund`.

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?

Provides a direct hint about an alternative source (`t2 fund`), but no explicit guidance on when to use this tool versus others. However, siblings are distinct operations, so confusion is minimal.

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