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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavior: "Read-shaped tools only (anything that buys, sells or writes refuses)" and "their data comes back as it is." It also mentions cross-chain parallel querying, which is useful beyond the structured metadata.

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 front-loaded with the core action, which is good, but the middle sentences become rambling and confusing, including the truncated "Bitcoin ad" and the awkward "live seat on The Wall (hosted by them)." It earns no penalty for length, but structure and clarity suffer.

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?

This tool has an open schema, no output schema, and unclear parameter semantics, so the description should compensate but does not fully do so. An agent can infer that `addresses` should be provided, but cannot determine its format or what the returned portfolio data will look like, leaving the invocation under-specified.

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 schema is an empty open object with no formal parameters, so the description carries the burden of explaining invocation. It names `addresses` and gives a partial condition, but it never states the expected type, shape, or formatting of that parameter, leaving a real gap for an agent trying to call the tool correctly.

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 states a clear action: "Query one address, or a whole set of them, across many chains in parallel." This gives a specific verb, resource, and behavior, and the title "portfolio" reinforces the intent. It is not a 5 because it never explicitly says the result is a portfolio of holdings or balances, leaving some ambiguity versus sibling tools like balance and history.

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 gives some usage context: pass `addresses` when a user holds multiple address types, and it notes this is a read-only surface. However, it does not explicitly name alternatives, state when not to use this tool, or explain how it differs from the many other singularityagent__ read tools.

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