spraay_portfolio_tokens

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

Annotations already declare readOnlyHint and openWorldHint. The description adds cost per call and instruction to pass fields directly, but this is minimal. No disclosure of error handling or output details.

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 very short but not effectively front-loaded. 'Portfolio tokens' is a noun phrase that doesn't earn its place. The cost and read-only info are useful, but overall it's under-specified.

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 simple tool with 2 params and output schema, the description still fails to explain the core purpose. An agent would have incomplete context to invoke correctly, as it doesn't clarify what the tool returns.

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%, so baseline is 3. The description does not add meaning beyond the schema; schema descriptions are basic ('address parameter'). No elaboration on parameter format or acceptable values.

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 says 'Portfolio tokens' without a verb, making it unclear if the tool retrieves, lists, or something else. The name suggests portfolio, but it does not specify the action, unlike typical tool descriptions that start with 'Get' or 'List'.

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 relative to alternatives like spraay_tokens or spraay_portfolio_nfts. It only states it's read-only and costs money, but not context for choosing.

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