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

With no annotations, the description carries the full burden, but this is a zero-parameter read-only lookup with little risk to disclose. It does add one useful behavioral detail: the contract address is conditional ("if launched"), signalling that a missing or pre-launch value is a legitimate outcome rather than an error. It says nothing about freshness guarantees or what happens if no facts exist yet.

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 sentences: the first front-loads purpose with a compact content enumeration, the second is a single-sentence activation rule. Nothing is redundant with the title or restates the tool name without adding information.

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 no-parameter, no-output-schema retrieval tool, the description gives enough for an agent to decide to call it and to anticipate the covered domains. The main remaining ambiguity is scope relative to siblings (e.g. what belongs in get_faq or get_latest_news instead), which the description leaves implicit.

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 the baseline is 4. The description appropriately spends no words on parameter semantics and instead describes the fixed content the call returns.

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 the resource precisely ($ODDI facts for Oddi Forge) and enumerates the covered content: launch status, contract address, tokenomics, vesting, rewards, safety rules and links. That makes it clearly a canonical-facts lookup rather than news, FAQ, or team info, though it doesn't explicitly name which sibling to use for adjacent questions.

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?

"Use this before saying anything about $ODDI" is a direct, actionable usage rule that tells the agent when to reach for this tool. It does not state when NOT to use it or point at alternatives like get_faq or get_latest_news for non-fact content, which is the only gap.

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