Retrieve the wallet infos about the connected P-Link account (Solana wallet address, wallet balance, tokens detail)

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

The description does not disclose behavioral traits beyond what annotations provide. Annotations indicate readOnlyHint=true, implying a safe read operation, which the description aligns with by using 'retrieve'. However, it adds no additional context such as rate limits, authentication needs, or data freshness, relying solely on annotations for behavioral insight.

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 a single sentence that repeats the title verbatim, adding no new information. This is inefficient and under-specified, failing to earn its place with meaningful content, though it is not overly verbose.

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 the tool has annotations (readOnlyHint) and a well-documented input schema but no output schema, the description is minimally complete. It covers the basic purpose but lacks details on return values, error handling, or integration with sibling tools, making it adequate but with clear gaps for an agent to understand full context.

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?

The description adds no meaning beyond the input schema, which has 100% coverage for the single parameter 'pubk'. The schema already describes it as an optional Solana address defaulting to the connected wallet. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate with extra parameter details.

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?

Tautological: description restates name/title.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not clarify if this is for general wallet info versus more specific tools like 'get_wallet_history' for transaction history or 'get_private_key_of_wallet' for sensitive data, leaving the agent without explicit usage context.

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