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

With no annotations, the description carries the full burden, and it does disclose two behavioral facts: the call returns an access refusal rather than data, and coverage is excluded. However, it never explains why access would be refused, what the refusal structure contains, or whether any data is ever returned, leaving the core behavior ambiguous.

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?

It is only two sentences and front-loads the refusal behavior, so it is not bloated. But the brevity comes at the cost of under-specification: the second sentence narrows scope before the first has established what the tool does.

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-param tool with no annotations and no output schema, the description is the only source of truth about the return payload, and it does not describe what the 'structured access refusal' contains or whether a successful listing is possible. An agent would have to call it blind to learn its behavior.

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 nothing for the description to disambiguate. No param claims are made that would conflict with the empty object schema.

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 name implies listing RWA assets, but the description never says what data is returned; instead it says it returns a 'structured access refusal for the rwa family.' That may be a permission-denied payload rather than a listing, so an agent cannot tell what the tool actually produces or how it differs from list_ondo_assets, list_baskets, or list_markets.

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?

There is no guidance on when to call this versus the many sibling list_* tools. The only directional statement, 'Does not return coverage,' reads as a scope exclusion but is not framed as a selection criterion, so nothing tells the agent when this tool is the right choice.

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