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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral content: it is an interactive guide exposing 'what you can ask', 'what you can do', tool selection, and a fee-on-transfer rule. It does not describe return formatting, but for a zero-parameter guide tool this is minor.

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?

Front-loaded with the key scoping fact ('Start here for $BOBAI itself') and the alternative is parenthesized early. The final sentence ('Call it first when you are unsure...') restates the routing already implied, so it is slightly redundant but still short and efficient.

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-param, no-output-schema orientation tool, the description covers purpose, scope, alternative routing, and what the guide surfaces. Nothing essential for calling it correctly is missing; only return-shape detail is absent, which is acceptable here.

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 no parameters, so there is nothing to document and the baseline is 4. The description correctly implies a stateless, argument-free 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?

States a specific resource ($BOBAI) and function (interactive orientation guide that tells you what to ask and which tool to call). It explicitly scopes itself against the sibling bsc_token_preflight for other tokens, so an agent can distinguish it without opening a 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?

Gives an explicit when-to-use ('Call it first when you are unsure which $BOBAI tool fits') and an explicit when-not/alternative (any other token → bsc_token_preflight). Routing conditions are fully stated, leaving nothing to inference.

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