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

No annotations are provided, so the description carries the full behavioral burden. 'Get supported...' clearly implies a non-mutating read, so the safety profile is inferable, but nothing is said about result size, pagination, or whether results are live/static data.

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 sentences, zero filler, with the core action front-loaded and the filtering capability second. Nothing is wasted.

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 simple read-only lookup with a fully documented 4-parameter schema and no output schema, the description covers what the tool returns and how it can be narrowed. It could note whether results are paginated, but nothing essential for a correct call is missing.

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?

Schema description coverage is 100%, so all four parameters (limit, search, symbol, network) are already fully documented in the schema. The description restates three of the filters without adding format, matching, or default semantics, which is the baseline expectation when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get supported cryptocurrencies and networks') with a clear scope (on Flashift), which is unambiguous against the transaction/provider-focused siblings. It does not explicitly contrast with any sibling, but the resource is distinct enough that no differentiation is needed.

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?

'Optionally filter by symbol, network, or search keyword' signals the usage mode (browse-all vs. narrow by filter), which is the relevant guidance for a listing tool. However it gives no when-to-use/when-not context, prerequisites, or alternatives among the sibling tools.

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