market_get_wallet_balance

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

No annotations provided. Description only states it is a get operation; it does not disclose return format, supported blockchains, or potential errors. Minimal behavioral disclosure.

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?

Single sentence, 11 words, front-loaded with action and resource. No redundant phrasing.

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?

Tool has no annotations, no output schema, and minimal description. For a balance tool with many siblings, this is insufficient to guide correct selection or understand the response. Should mention return contents or relationship to 'all' variant.

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 descriptions cover both parameters (100% coverage). Description adds nothing beyond 'specific blockchain', which merely echoes the connectionId. Baseline 3 applies.

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?

Clear verb 'Get' with specific resource 'balance data for a wallet address on a specific blockchain'. It distinguishes from sibling market_get_wallet_balances_all by scoping to a single chain, but 'balance data' is slightly ambiguous (could imply native or token balances).

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 on when to use this tool versus chain-specific balance tools or market_get_wallet_balances_all. Usage must be inferred from the name and sibling list, not stated.

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