get_xstocks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds nothing beyond that: it does not mention pagination behaviour, whether the list is exhaustive, how chain filtering affects results, or any rate/coverage caveats that would matter for an open-world directory listing.

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?

A single short sentence with no filler and the key noun front-loaded, which is efficient. But the brevity crosses into under-specification for a tool with filtering and paging behaviour that the reader needs to know about.

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?

There is no output schema, so return values are undocumented, and the three request parameters are undocumented in both schema and description. For a list/pagination tool with an openWorld annotation, the definition omits what the agent needs in order to call it correctly.

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 0% and none of the three parameters (page, limit, chain) are explained in the description, not even their existence. With three fully undocumented parameters the description should carry the burden and does not, so this is worse than the baseline for fully documented or zero-parameter tools.

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 ('List') and a specific resource ('tokenised equities (xStocks)'), so the agent knows exactly what is returned. It does not, however, contrast itself with the many other token-listing siblings such as get_trending_tokens, get_top_tokens, or get_zora_tokens, so differentiation is left to inference.

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 offers no when-to-use guidance, no prerequisites, and no pointer to alternatives among the many list-style siblings. An agent must guess whether this is a full directory listing or a filtered one.

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