Get 1Shot Capabilities

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

No annotations are provided, so the description carries the full behavioral burden. 'Fetch' implies a read, but it does not describe what a capability payload contains, whether any auth or registration is required, or whether results are cached/rate-limited.

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?

Two short sentences with the primary action front-loaded. The second sentence is slightly tangential but still earns its place as a related-tool note; nothing is padded.

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?

With no output schema and no annotations, the description should do more to explain what capabilities are returned and why an agent needs them before relaying. It is minimally adequate for a zero-required-param read tool but leaves the consumer to infer the value.

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% and the single chainIds parameter is fully documented in the schema, including the Base 8453 default. The description's 'one or more chains' restates the schema without adding format or syntax detail, so baseline 3 applies.

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 ('Fetch 1Shot public relayer capabilities') with the scope 'for one or more chains'. This distinguishes it from the other oneshot siblings (fee data, relay calls, status), though it doesn't name them explicitly.

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?

There is no statement of when to call this versus agent_oneshot_get_fee_data, agent_oneshot_relay_calls, or agent_oneshot_get_status. The second sentence only cross-references agent_prepare_delegation's behavior, which is context, not usage guidance for this tool.

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