sui_get_coin_metadata

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 only restates the basic action and does not disclose aspects like whether the operation is read-only, how invalid coin types are handled, or what the response structure looks like. This is minimal for a metadata lookup tool.

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, focused sentence without redundant words. It is appropriately concise for a simple tool, though it could be slightly more informative without becoming verbose.

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 is low complexity with one parameter, but there is no output schema and the description does not compensate by explaining what metadata is returned. It also lacks usage context or relation to other Sui tools. A more complete description would mention typical fields like name, symbol, and decimals.

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 provides 100% coverage for the single parameter 'coinType' with its default value and description. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies. No further clarification or examples are given.

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 'Get metadata for a coin type' uses a specific verb (Get) and resource (metadata for a coin type), clearly distinguishing it from sibling tools like sui_get_balance or sui_get_object. It is not a tautology and conveys the core function, though it does not enumerate what metadata fields are included.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is the right tool for coin metadata, nor does it point to siblings for related operations like balances or transactions. The description offers no context about appropriate use cases.

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