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

Annotations already mark it read-only, open-world, non-destructive, and non-idempotent, but the description adds substantial context: return shape, 404/422 error behavior, charging rules, free failures, and that repeats are not free. These details go well beyond the annotations and help the agent understand cost and error semantics.

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 front-loaded with the core definition and usage guidance, and every major clause adds useful information about token input, errors, or pricing. It is dense and somewhat long, but appropriate for a paid multi-chain read tool with no output schema.

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 there is no output schema, the description sufficiently explains what is returned: allowance raw and in token units, plus unlimited-approval status. It also covers pricing, error behavior, and read-only semantics, leaving no critical gap for correct invocation.

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 the baseline is 3, but the description adds useful token semantics: token accepts a ticker or 0x contract, and missing contracts return 404 while non-ERC-20 tokens return 422. It does not add much beyond the schema for owner and spender, so it is strong but not exhaustive.

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 states a specific verb and resource: it returns ERC-20 token allowance on Gnosis, including raw and token-unit amounts plus unlimited-approval status. It also distinguishes the tool from gnosis_token_balance, so an agent can select it without opening sibling schemas.

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?

It gives explicit use cases: checking an approval before a swap or auditing risky open approvals. It also names the alternative tool for the owner's balance, gnosis_token_balance, making the when-to-use boundary clear.

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