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

With no annotations, the description carries full responsibility for behavioral transparency, yet it only describes the content ('what this server sells and its current limits') and not side effects, auth, or whether the call is read-only. The name hints at info, but the description itself offers no behavioral guidance.

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?

At two short sentences—'Start here. What this server sells and its current limits.'—the description is front-loaded with intent and contains zero filler.

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 zero-parameter overview tool, the description tells the agent where to start and what it will learn, which is adequate for calling it. It could be more complete by detailing the output contents, but the generic nature of 'what the server sells and its current limits' makes that less critical.

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 input schema has zero parameters, so there is nothing for the description to add beyond the schema. Per the baseline for 0-parameter tools, this is adequately handled.

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 phrase 'Start here' combined with 'What this server sells and its current limits' clearly identifies this as an entry-point overview tool for service capabilities, distinguishing it from siblings like gas_price that target specific data. It lacks an explicit verb like 'get' but conveys the resource clearly.

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 instruction 'Start here' explicitly directs the agent to invoke this first, providing clear usage context. It does not mention when to avoid it or list alternatives, so it stops short of a full 5.

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