get_portfolio

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds valuable detail: returns balance, price, EUR value, sorting behavior (default field 'value', alias parameter 'sort'). This goes beyond the annotations, though it does not disclose pagination or limits.

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 description is concise, front-loaded with the main purpose, and uses only three sentences with no unnecessary words. Every sentence adds value.

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?

Given the tool's simplicity, presence of an output schema, and annotations covering safety and variability, the description provides sufficient context. It could mention that the portfolio is for the authenticated user, but that is implied. Slight gap on handling null sort parameters.

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 coverage is 0%, but the description explains that sorting is by 'value' (default) or 'name' and that 'sort' is a CLI-compatible alias. This partially compensates for missing schema descriptions, but does not list exact allowed values or interaction between sort_by and sort parameters.

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 clearly states the tool retrieves an aggregated portfolio view with EUR valuations, listing returned fields (balance, price, EUR value) and sorting options. This distinguishes it from sibling tools like get_asset or list_wallets which are more granular.

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 does not provide guidance on when to use this tool versus alternatives like get_asset or list_trades. It does not mention prerequisites, limitations, or typical use cases, leaving the agent to infer usage context.

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