Account Overview

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds value by detailing the five return sections (summary, balances, positions, info, margin), giving the agent a concrete picture of what to expect beyond the 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?

Extremely concise: one introductory sentence, one usage directive, and a bulleted list of return sections. Every sentence earns its place, and the structure is highly scannable.

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?

Given there is an output schema (not shown but referenced in context signals), the description need not explain return values beyond listing the sections. It also clarifies that this tool consolidates multiple sibling calls, which is key context. Fully complete.

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?

Input schema has zero parameters, so no additional meaning is needed. Baseline is 4. The description does not need to explain parameters.

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 it provides a 'complete snapshot' of account details, listing specific categories (margin health, balances, positions, fees, margin methodology). Explicitly differentiates from sibling tools like paradex_account_summary, paradex_account_balance, and paradex_account_positions by positioning itself as a consolidated alternative.

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?

Directly advises 'Use this instead of calling paradex_account_summary, paradex_account_balance, and paradex_account_positions separately', providing explicit when-to-use guidance. No when-not-to is needed given it is a comprehensive read-only endpoint.

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