wallet_overview

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

Excellent. Even though no annotations exist, the description fully carries the burden by disclosing the async 'computing' state with retry_after_seconds and the instruction to poll after the delay, plus the design behavior of returning a digestible summary for heavy wallets. This is exactly the non-obvious behavior an agent cannot infer on its own.

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 well organized: headline purpose, supporting detail, async edge case, then parameter doc. It earns most of its sentences, and the computing-notice paragraph is vital. It loses a point because the parameter semantics ('Accepts... OrcaLayer nickname') are redundantly restated in the Args section after already appearing in the intro.

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 tool with one parameter, no output schema, and no annotation support, the description is nearly complete: it covers accepted inputs, return-style behavior, the polling/retry contract, and the rationale for compact output. The only minor omission is that it never shows a sample response shape or mentions what happens on a malformed address, which is a marginal gap.

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 0% schema description coverage, the description is solely responsible for parameter meaning, and it fully delivers: the address parameter's accepted forms ('0x wallet address or OrcaLayer nickname') are documented both in the intro and the Args block. The bare schema only reveals a string titled 'Address,' so the description's value-add is substantial.

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 opening line uses a specific verb and resource: 'Summarize one wallet's trading profile and performance.' It names the domain (Polymarket), the accepted inputs (0x address or OrcaLayer nickname), and the output shape (compact summary with identity, activity, P&L stats). The phrase 'one wallet' plus the contrast with 'full raw record' sharpens the scope without ambiguity.

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 clear decision context: choose this tool when you want aggregate stats rather than the full raw record, and it explains the compact-summary tradeoff for heavy wallets. However, it never names sibling tools like wallet_positions or whale_alerts explicitly, so an agent must infer the routing rather than have it spelled out.

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