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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by identifying the content as static press-kit facts rather than market data and noting that it includes the official contract and project disclaimer. It does not contradict the annotations.

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 deliver the tool's content, source, and exclusion with no wasted wording. The key scope limitation, "not market data," is front-loaded effectively.

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 simple no-parameter, read-only overview tool, the description is mostly complete about what it returns. However, because sibling tools separately expose contract and disclaimer data, the description does not clarify how this overview relates to those tools or whether it duplicates them, leaving a notable completeness gap.

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 100% schema description coverage, so there are no parameter semantics to explain. The description appropriately avoids unnecessary parameter detail, matching the no-input design.

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 states that this tool returns an overview of American Bully ($BULLY), including official contract and disclaimer content, and distinguishes it from market data. It is specific about the resource and content type, but it does not differentiate the tool from siblings such as check_contract and get_disclaimer, whose content it appears to overlap with.

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 "Static facts from the press kit, not market data" gives an implied usage boundary and one exclusion. However, it does not explain when to use this overview instead of check_contract, get_disclaimer, or get_official_links, so the agent must infer the right choice among siblings.

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