railx_get_portfolio

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

The annotations already declare readOnlyHint=true, and 'Read-only' merely restates that, adding no value. The description says nothing about whether the wallet must be known/auth'd, whether results are on-chain live or cached, pagination/limits on symbols, or what happens with unknown symbols.

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 very short sentences, front-loaded with the core purpose. It is efficiently sized, though the trailing 'Read-only' is a pure restatement of the annotation and earns no place.

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?

With no output schema and 0% parameter coverage, the description should carry more of the load. It does not explain the return shape (balances plus positions), the effect of the symbols filter, or the meaning of includeZero, leaving the tool under-specified for an agent.

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 the description supplies no parameter meaning at all. Three parameters (wallet address, symbols filter, includeZero) are left entirely for the agent to infer from names, which is especially costly for how includeZero interacts with symbols filtering.

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+resource: reads wallet balances and Stock Token positions. An agent can tell this is a portfolio snapshot tool rather than a price, asset, or trade-plan tool. It does not explicitly name a sibling to differentiate against, so it stops short of 5.

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 when-to-use guidance, no conditions that select this tool over railx_get_asset or railx_get_trade_plan, and no prerequisites. Usage is only implied by the phrase 'wallet balances and positions'.

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