transferCoinListQuery

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

The description correctly identifies this as a read-only query with no side effects. With no annotations, it adequately covers behavioral traits (constraints, no mutation).

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 sentences, front-loaded with the core action, no extraneous information. Every sentence adds value.

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 query tool with no output schema, the description covers purpose, parameters, and constraints. It does not mention return format or error conditions, but is sufficient for basic usage.

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 description adds meaning to both parameters by naming them and stating constraints (cannot be same, must be supported). Schema has 0% description coverage, so description compensates well, though possible values or examples are missing.

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 verb 'Query' and the resource 'list of coins that can be transferred between specified account types'. The constraints differentiate it from sibling tools like CoinListQuery.

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 explicit constraints (account types cannot be the same, must be supported) but does not mention when to use this over other query tools like interTransferListQuery.

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