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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description correctly does not contradict it. The description adds the word 'active', which implies inactive/delisted assets are excluded, but says nothing about ordering, freshness, or whether the list is paginated or cached.

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 purpose is front-loaded in the first four words, which is good structure. However, the remaining ~50-item enumeration dominates the description and largely restates what the tool itself returns, which will also go stale as assets are listed or delisted; a pointer such as 'call this to discover valid symbols' would have been tighter.

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 zero-parameter tool with no output schema, the description does tell the agent what it will get back (the set of tradable analytics assets), which is the main thing that would otherwise be unknown. It is slightly incomplete in not clarifying the relationship to get_metrics_list, but nothing needed to call it 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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to compensate for. The enumerated symbols function as the return-value vocabulary rather than as input semantics.

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 ('List active analytics assets') and then enumerates exactly what an asset is, so the agent can distinguish this from the metrics-oriented siblings (get_metrics_list, get_metric_metadata) by resource alone. It stops short of naming those siblings or explaining the division of labor between them.

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?

Usage is only implied: the enumerated symbols suggest this is the tool to call to discover valid symbol strings before calling fetch_metric or get_asset_metrics, but the description never states that or names an alternative. There are no explicit when-to-use or when-not-to-use conditions.

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