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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by listing exactly what kind of links and resources will be surfaced, including a live burn audit log, which helps the agent predict the output.

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, dense sentence with no fluff. The official-link framing is front-loaded and every listed item adds specificity.

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 link tool, the description is sufficiently complete to guide invocation and interpret results. The only minor gap is that 'llms.txt' is not explained, but it is a recognized artifact and the overall coverage is strong.

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, so the schema fully covers parameter expectations. The description appropriately focuses on output content rather than parameters, which is exactly what the agent needs.

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 clearly identifies the resource as 'Official $BOBAI links' and enumerates specific content (website, BscScan contract, X, Telegram, etc.), making it easy to distinguish from sibling data-focused tools. It lacks an action verb like 'retrieve' or 'return', but the intent is unambiguous.

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 implies this tool is for fetching official BOBAI-related URLs and resources, but it does not explicitly state when to use it versus siblings like bobai_purchase_guide or bobai_token_info. There is no exclusion or routing guidance, so the agent must infer the appropriate use case.

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