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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful behavioral context by disclosing explicit capability flags (read-only; cannot send, retry, or sign) and clarifying that providers require connected credentials, which goes beyond the structured fields.

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 dense sentence that front-loads the purpose and then packs the output categories into a parenthetical list, followed by a helpful use cue. It is efficient, though the long first sentence is somewhat overloaded with details.

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 no parameters, an output schema, or nested objects, the description is complete: it enumerates the categories of information the tool provides (assets, chains, providers, capability flags) and gives a clear decision rule for when to invoke it. An agent has enough context to call and interpret the result without additional documentation.

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 parameters and the schema coverage is trivially 100%, so there is no parameter meaning for the description to add. With no parameters, a baseline of 4 is appropriate, and the description instead invests its space in explaining the result content.

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 action ('List'), the resource ('what Trace supports and can do'), and enumerates concrete categories: assets, chains, providers, and capability flags. It also implicitly distinguishes itself from trace_payment by framing itself as the scope-checking entry point, so an agent can tell it apart from siblings.

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 explicitly says to call this tool 'when unsure whether a payment is in scope for trace_payment,' which is a clear usage trigger and names a sibling alternative. However, it does not give an explicit when-not-to-use statement or contrast with get_trace, so it stops just short of full alternative routing.

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