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

Annotations already establish that this is a read-only, idempotent, closed-world lookup, so the description does not need to repeat safety semantics. It adds useful behavioral context by describing the returned data inventory and the `<entityId>.<hex>` address-handle convention that applies across tools. It does not disclose limits, pagination, freshness, or response-size behavior.

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 definition is dense but front-loaded, beginning with the core resource and then enumerating the returned data categories. Every sentence carries useful information, though the long return-value list is somewhat list-heavy and could be easier to scan with structure.

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?

Because there is no output schema, the description carries the burden of explaining what comes back, and it does so with a broad inventory of addresses, roles, evidence, holdings, positions, moves, totals, and 30-day trading. It is nearly complete for selection and invocation, but omits practical caveats such as pagination, limits, or data freshness.

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 100%, so both parameters are already documented, including the network enum and testnet null-value caveat. The description adds meaning beyond the schema by explaining valid id provenance and the entity-id handle format.

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 that this retrieves one named entity by id and enumerates the returned profile, holdings, positions, moves, totals, and trading history. It is distinguishable as a detail lookup rather than a search or graph tool, though it does not explicitly contrast itself with get_identity, get_entity_graph, or get_entity_pnl.

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?

It explains where the required id can come from: search_entities, get_identity, or an `entity` field. However, it gives no explicit when-to-use guidance relative to sibling tools and no exclusions or conditions that would route an agent between this and get_identity, get_entity_graph, or get_entity_pnl.

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