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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by specifying exactly what data is read and positioning the operation as a pre-signing prerequisite. No contradictory behavior is claimed, and the read-only nature is consistent with 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?

One dense sentence with a clear leading verb and a structured list of returned items. There is no filler, repetition, or ambiguity, and the most important idea ('Read') comes first.

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 parameterless, read-only getter with rich annotations, the description is nearly complete. It names the full set of returned fields and the intended timing. It does not describe the response envelope or formatting, but that is not critical given the explicit field list and the absence of an output schema.

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 tool has zero parametersarenas, so the schema trivially covers 100% and there is no parameter ambiguity. The description's field list effectively substitutes for any need to explain parameter semantics.

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 names a specific verb ('Read') and a concrete resource (native config), then enumerates the exact components it returns: chain, token, EIP-712 domain, action types, and payment mode. This is readily distinguishable from sibling tools like get_action_schema or get_posting_instructions, which target different resources.

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 phrase 'before signing' gives clear contextual guidance for when this tool is appropriate, tying it to the signing workflow. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5, but the intended usage is unambiguous.

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