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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable behavioral detail beyond the schema: the leaderboard source, the current-positions summary, and that values are Decimal.js decimal strings. No contradiction with annotations.

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?

A single front-loaded sentence with no redundant filler. Every clause contributes either the target, the scope, or an output-format detail, making it efficient and easy to parse.

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 one-parameter, read-only tool with an output schema and rich annotations, the description is nearly complete: it names the source, scope, and value representation. It only lacks explicit routing guidance against sibling wallet tools, but that gap is already accounted for in usage guidelines.

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%, and the schema already documents walletAddress's pattern, public proxy nature, and the Google sign-in caveat. The description adds no further parameter-level meaning, so the baseline 3 is appropriate.

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?

Clearly states the verb ('Get') and resource ('all-time public wallet PnL'), and adds useful scope: source (overall leaderboard), current positions summary, and decimal-string values. It is specific but does not explicitly differentiate itself from the near-duplicate sibling 'get_wallet_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?

No explicit when-to-use or when-not-to-use guidance is provided. The 'public' and 'all-time' qualifiers imply the intended case, but no alternative tool is named and no exclusion condition is stated, leaving the agent to infer selection among many wallet-related siblings.

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