wallet_profile

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that the tool 'gets' a profile/analysis, which is a read action implied by the verb, but does not disclose whether it's a read-only operation, whether it queries multiple chains, response size/format, or any rate/permission constraints. There is no meaningful behavioral information beyond the name.

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 brief single sentence with no fluff, but its brevity sacrifices essential detail. It is under-specified rather than genuinely concise, as an agent would need more context to understand the tool's full purpose.

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?

There is no output schema, and the description does not clarify what the 'profile and behavior analysis' actually includes (e.g., transaction history, token balances, labels, risk scores). Given that many similar wallet tools exist, this lack of detail makes the tool's value and output unpredictable for an agent.

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 covers both parameters (address and chain) with descriptions, so the baseline is 3. The tool description adds no additional parameter-level detail, such as address formats or chain default behavior, leaving the schema to do the work.

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 identifies the action (get) and topic (wallet profile/behavior analysis), but 'comprehensive' is vague and does not specify what aspects of the wallet are covered. It fails to distinguish this tool from siblings like get_wallet_portfolio or get_wallet_activity, leaving the agent unsure of its exact scope.

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?

No guidance is provided regarding when to use this tool versus alternatives. The description is generic and lacks any context about use cases, prerequisites, exclusions, or preferred scenarios, so the agent must infer usage entirely from the tool name.

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