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

With no annotations, the description carries the full load, and it does useful work: it establishes this is a read ('read from PairCore on BSC'), identifies the authoritative on-chain source, and specifies exactly what state is reflected rather than claiming cached or computed values. It omits auth requirements, freshness/latency, and failure behavior if BSC is unreachable, which are the remaining gaps for a no-annotation tool.

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, front-loaded with what the tool is and where the data comes from, followed by a compact enumeration of return fields. Every item in the list corresponds to a distinct piece of state an agent would need; nothing reads as filler.

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?

There is no output schema, so the description must explain return values, and it does so exhaustively for this tool's scope: sale counts against the fixed 888 supply, window and sale open flags, public sale progress, and LP creation status. For a zero-parameter read of a well-defined on-chain round, an agent has everything needed to decide whether to call it and how to read the result.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema coverage signal of 100% is trivially satisfied by an empty object.

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 a specific resource and scope: 'Live status of the PairMine Genesis round' plus the data source 'read from PairCore on BSC'. It then enumerates the concrete facts returned (miners sold/remaining out of 888, window and sale open state, progress, LP creation), which lets an agent distinguish it from static siblings like project_info or tier_price. It stops short of explicitly naming those siblings as the alternatives, which keeps it from a 5.

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?

There is no explicit when-to-use or when-not-to-use statement and no reference to the sibling tools (check_eligibility, tier_price, mint_instructions) that an agent must choose between. The usage context is inferable — this is the pre-mint status check — but the description leaves that inference to the agent.

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