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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds domain context (fees, minimums, signing flow) but says nothing about return format, freshness, or size, so it earns only moderate credit beyond 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?

Two short sentences, front-loaded with the imperative 'Start here.' and then an efficient enumeration of covered topics. No filler or repetition.

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 parameters, the description carries the burden of setting expectations, and it does so by enumerating the content areas the overview covers. An agent knows what it will get and when to use it; only the actual return format remains implicit, which is a minor gap.

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 takes zero parameters, so per the baseline this dimension is a 4. There is no parameter semantics to document, and the empty schema is consistent with the description's framing as a parameterless info-retrieval call.

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 exactly what this tool returns—an orientation document covering 'What Panda offers on Base, which tool does what, fees, minimums, how signing works and every contract a transaction may touch.' This makes it unmistakably distinct from all the build_*/get_* action siblings, which an agent can recognize without opening any schema.

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?

'Start here.' is an explicit, directive when-to-use signal, telling the agent to call this first before acting. It does not name when-not-to-use or specific alternatives, but for an entry-point orientation tool the context is unambiguous.

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