spraay_analytics_wallet

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, establishing a safe read operation. The description adds value by specifying the cost, the Base chain focus, and the components of the profile (balances, age, classification, portfolio), providing behavioral context 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?

The description is a single, well-structured sentence that front-loads the primary action ('Get a comprehensive wallet profile') and efficiently conveys scope, content, and cost. No wasted words.

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?

The tool has an output schema (not shown) and the description lists key data fields, so the description is sufficiently complete for an agent to understand the tool's output. However, given the large number of sibling tools, a brief note on differentiation would enhance completeness.

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 parameter 'address' is already well-described in the schema with a pattern and example. The description does not add additional meaning or constraints beyond the schema, so a baseline score of 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?

The description clearly states the verb 'Get' and resource 'comprehensive wallet profile', listing specific data points (ETH + token balances, wallet age, etc.). However, it does not explicitly distinguish this tool from the sibling 'spraay_agent_wallet_info', which may cause confusion.

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 mentions the cost ($0.005 USDC), which is a practical guideline. However, there is no explicit statement about when to use this tool versus alternatives, nor any exclusion criteria. Usage context is implied but not fully articulated.

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