my-coins

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

With no annotations, the description conveys the read-only nature through the verb 'List' and states the return data includes live market data. It does not mention any exclusions or edge cases, but for a simple list operation this is sufficient.

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 front-loaded sentence that efficiently communicates both the action and the returned data without wasted words.

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?

Given the zero-parameter interface and simple read-only nature, the description fully explains what the tool does and what it returns. No output schema exists, but the listed fields (price, market cap, volume) cover typical market data.

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 tool has zero parameters, so there is no need for parameter-level guidance. The description clarifies the scope ('from this machine') and return data, which is more than the empty schema provides.

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 ('List') and clearly identifies the resource ('every coin launched from this machine'). It distinguishes from siblings like 'launch' (creation) and 'wallet' (balances) by focusing on the machine's launched coins and adding live market data.

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 clearly implies when to use: to view all previously launched coins from this machine. It does not explicitly mention alternatives, but the scope is unambiguous in context of sibling tools like 'launch' and 'wallet'.

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