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

The description does not disclose whether the tool performs read-only operations, requires authentication, or has side effects. The mention of 'signed wallet' implies some interaction, but no explicit statement about data handling or limitations beyond the trial count.

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 brief and to the point, with only two sentences. The inclusion of the trial note is extra but not verbose. It is well-structured for quick parsing.

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?

The description lacks essential context: what chains are supported, what the profile includes (e.g., balances, tokens, activity), and what output format to expect. Without this, an agent cannot reliably decide when to invoke this tool.

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?

Both parameters 'wallet' and 'address' have nearly identical descriptions ('Wallet to process' and 'Address to process'), which is redundant and confusing. The schema provides no additional details, leaving the agent unclear about the distinction between the two inputs.

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 it provides a multi-chain wallet profile. The phrase 'wallet profile' conveys the tool's core function, and the emoji adds a friendly tone. It is distinct enough from sibling tools like wallet-activity or wallet-balance, though it could be more specific.

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 given on when to use this tool versus other wallet-related tools (e.g., wallet-activity, wallet-report). The '5 free trial calls per signed wallet' note is a business rule, not a usage guideline.

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