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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds useful scope by listing the categories of data returned, which matters because there is no output schema, but it does not disclose aggregation limits, latency, or response structure.

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 a single well-formed sentence with the core scope front-loaded and no redundant wording. Every phrase contributes to clarifying what the operator footprint contains.

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?

For a broad aggregator with no output schema, the description enumerates the major data categories, which is helpful but remains high-level. It omits details about result shape, pagination, and when the aggregate is preferable to narrower sibling tools.

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?

With a single wallet parameter and 100% schema description coverage, the schema already explains the parameter format. The description reinforces that the wallet can be any address but adds no further semantic detail such as supported chains or address normalization.

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 resource and scope: an aggregated operator footprint for a wallet, including owned agents, trust scores, sybil signals, wallet intelligence, and MCP servers. It is identifiable despite the vague tool name 'entity', but it does not explicitly differentiate itself from siblings like trust_check or reviewer_wallet.

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 implies the tool is used for any wallet address, but gives no explicit guidance on when to choose this comprehensive footprint over narrower siblings such as trust_check, address_age, or reviewer_wallet. No exclusions or alternatives are stated.

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