sui_get_total_supply

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the action without mentioning that it is a read-only operation, the return format, error behavior, or any edge cases. The verb 'get' implies read, but no explicit behavioral context is given.

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 ('Get total supply of a coin type') that is front-loaded and contains no redundant or filler words. It is appropriately sized for a simple getter tool.

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 adequate for a simple read tool but has clear gaps: there is no output schema to describe the return value, and no annotations. It does not explain the response format, how to interpret the supply value, or how this tool differs from other Sui tools. This makes it minimally viable but incomplete.

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 includes full coverage for the single parameter coinType, with a default value and a description. The tool description adds no additional semantic information beyond what the schema already provides, 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 uses a specific verb and resource: 'Get total supply of a coin type.' This clearly distinguishes it from sibling tools like sui_get_balance (which gets an address balance) and sui_get_coin_metadata (which gets coin metadata).

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, scenarios, or refer to sibling tools such as sui_get_coin_metadata, which might also be relevant when querying coin information.

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