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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds scope ('complete portfolio') and the breadth of what is aggregated, but says nothing about cost, latency, or behavior on unknown/empty addresses.

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 front-loaded sentence with no filler; the resource and the enumeration of returned data are the only content and both earn their 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, the description compensates well by enumerating the returned categories (properties, loans, orders, credit history, total value). What is missing is any note on aggregation behavior or prerequisites, but for a simple single-address read it is largely sufficient.

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?

Only one parameter with 100% schema description coverage ('Ethereum wallet address (0x...)'), so the schema carries the semantics. The description adds no format, chain, or validation detail beyond the schema, making this a baseline 3.

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 and resource ('Get a wallet's complete Fabrica portfolio') and enumerates exactly what the result contains: properties, loans, orders, credit history, value. It does not name or contrast with any sibling, but the siblings (get_activity, get_property, get_protocol_stats) are distinct enough that disambiguation is not really needed.

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 never says when to call this versus alternatives such as get_activity or get_property, nor does it state preconditions (e.g. would scan a wallet that may have no history). Usage is only implied by the enumerated contents.

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