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

Annotations already declare read-only, open-world, and idempotent hints, so the bar is lower. The description adds useful context about the data source (MemeJob bonding-curve launchpad) and pagination behavior, which goes beyond the annotation basics. No hidden side effects are left unaddressed.

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?

The description is two concise sentences, leading with a clear purpose, followed by sort and pagination details. Every word earns its place, with no redundancy or filler, and the structure front-loads the most critical 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 read-only browsing tool with zero required parameters and a fully self-documenting schema, the description covers the core aspects: data source, sort options, and pagination. It does not describe the return shape, but the tool's nature as a list finder makes this acceptable, and the annotations cover safety and idempotency.

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 input schema provides 100% coverage of all four parameters with detailed descriptions, including defaults, ranges, and enums. The description merely restates the sort options and pagination in prose, adding no new meaning beyond what the schema already specifies. Baseline 3 is appropriate.

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 tool's function: browsing Hedera meme tokens on the MemeJob bonding-curve launchpad. It specifies the resource (Hedera meme tokens), the platform (MemeJob), and the operations (sort, paginate), distinguishing it from sibling tools like hederaFindTokens and other chain-specific meme coin finders.

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 usage for discovery feeds on the MemeJob launchpad, which clearly situates it among Hedera meme token tools. However, it does not explicitly state when not to use this tool or recommend alternatives, though the Hedera-specific scope already differentiates it from BSC or Solana meme tools.

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