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

Annotations already communicate readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds a little semantic context about what counts as a real asset, but it discloses no behavioral details such as cursor-based pagination, default limits, or that the response is a list. It does not contradict the annotations.

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 a single concise fragment with no fluffhol, and the example asset classes are useful. However, it is not a complete sentence and omits the core verb that would clarify the operation, so the conciseness comes at the cost of completeness.

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 four parameters, zero schema descriptions, and no guidance in the description, the tool is incompletely documented even though an output schema exists. An agent knows the operation is safe from annotations but cannot confidently determine how to use asset_class, cursor, or household_id, or how this list relates to get_real_asset.

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%, so the description carries the burden of explaining the parameters. It lists categories that likely correspond to asset_class values, but it never explicitly maps them to the asset_class parameter or explains limit, cursor, or household_id. The hint is useful but insufficient.

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 is a noun phrase defining the term ('property, vessels, aircraft, art and collections') rather than stating what the tool does with those assets. It restates the scope of the title without signaling that this is a paginated collection listing, and it does not differentiate from the sibling get_real_asset.

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 provides no guidance on when to call this tool versus alternatives such as get_real_asset or list_portfolio_positions. There is no mention of pagination, filtering by asset_class, or the fact that no IDs are required.

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