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 one important trait: the call yields an access refusal rather than data, and it explicitly excludes constituents and weights. That is meaningful behavioral information no structured field provides. However, it says nothing about why the refusal occurs, whether credentials/entitlement would change the outcome, or what the refusal payload contains.

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, front-loaded with the outcome and followed by the exclusion. Nothing is padded, though the brevity comes partly at the cost of the missing usage context rather than from disciplined trimming.

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 no-parameter, no-output-schema tool, the description should at minimum tell an agent what it gets back and whether calling is ever useful. It signals the refusal and the missing constituents/weights but leaves the return shape and the alternative paths unexplained, so an agent cannot confidently decide to call it.

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 per the baseline there is nothing for the description to disambiguate. It correctly implies no input is required. The listing behavior itself, not parameters, is what is under-explained.

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 opens with a specific verb and scope ("Returns the structured access refusal for the baskets family"), which is concrete, but it never explains what the tool actually does with baskets, so a reader cannot reconcile the name "list_baskets" with a response that is apparently always a refusal. It gives no differentiation from any of the 23 sibling tools, several of which (list_vaults_with_incidents, list_markets) follow the same listing pattern.

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 statement of when to call this tool, when not to, or which alternative to use for basket data. An agent has no basis to choose it over list_rwa or get_vault beyond guesswork from the name.

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