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

Annotations already declare the tool read-only and non-destructive, so the safety burden is covered. The description adds valuable behavioral context: it is interactive, surveys askable/doable actions, routes to the right tool, and warns about the fee-on-transfer rule.

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?

A single sentence that front-loads the critical 'START HERE' cue and packs in scope, tool-routing value, and the fee-on-transfer caveat without wasted words. Excellent structure for an entry-point guide.

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, read-only routing guide, the description delivers everything needed: when to start, what the guide covers, and the must-know fee-on-transfer rule. No output schema or parameter details are required, and annotations cover the safety profile.

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 empty schema is fully documented, so there are no parameter semantics for the description to clarify. Baseline 4 applies because the description has no additional burden here.

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 opens with 'START HERE' and clearly states the resource ($BOBAI) and purpose: an interactive guide covering what you can ask, what you can do, and which tool to call for each. This also differentiates it from sibling tools by positioning it as a meta/routing guide rather than a specific data lookup.

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 'START HERE' and 'for an agent that just discovered $BOBAI' gives explicit context for when to invoke this tool. It doesn't list exclusions or alternatives explicitly, but it clearly signals this is the entry point for tool selection among the siblings.

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