sodax_get_all_config

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

Annotations already provide readOnlyHint: true, openWorldHint: true, and destructiveHint: false. The description adds useful context about the scope of data returned (all chains, swap tokens, protocol settings) without contradicting annotations. It informs the agent that this is a safe, read-only operation that may return variable results.

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 of 17 words, front-loading the key action and resource. Every word earns its place, with no redundancy or fluff. Highly efficient.

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?

For a simple one-parameter tool with annotations and no output schema, the description adequately conveys what the tool returns and the one-call nature. It could be slightly improved by mentioning that the format parameter affects output presentation, but schema covers that. Overall complete given the tool's simplicity.

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 input schema has 100% coverage and clearly documents the 'format' parameter with enum values and default. The description does not add any additional meaning beyond the schema, so it meets the baseline expectation.

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 the resource 'full SODAX configuration', specifying it includes all supported chains, swap tokens, and protocol settings. This distinguishes it from sibling tools that retrieve specific subsets (e.g., sodax_get_supported_chains, sodax_get_swap_tokens), making the purpose highly specific.

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 implies usage for retrieving comprehensive configuration in one call, and the sibling list shows alternatives for specific data. However, it lacks explicit guidance on when to use this tool versus the more granular siblings, nor does it mention any prerequisites or exclusions.

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