sodax_get_hub_assets

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is consistent and adds useful context about the hub chain and spoke tokens. No contradictory information. The description complements annotations by specifying the data scope.

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, front-loaded with core action and resource. No unnecessary words. Could be structured with bullet points for options, but current form is still concise and readable.

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?

No output schema, yet the description does not explain what the returned 'assets' look like (structure, fields). For a tool that returns data, this leaves the agent guessing. Parameter descriptions are adequate, but return value documentation is missing.

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% with detailed descriptions for both parameters. The description restates the filtering intent but does not add new semantic meaning beyond what the schema provides. The enum for format is already clear in the schema. Baseline 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?

Description clearly states the verb 'Get' and the specific resource 'assets representing spoke tokens on the hub (Sonic) chain', with optional filtering by source chain. This distinguishes it from siblings like sodax_get_money_market_assets or sodax_get_supported_chains, which target different data.

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 explicit guidance on when to use this tool versus alternatives. While it mentions optional filtering, it does not differentiate from similar getters among the many sibling tools. The only hint is to call sodax_get_supported_chains for chain IDs, but this is a prerequisite, not a usage rule.

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