hyre-new-tokens

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

No annotations are present, so the description bears the full burden. It adds behavioral context with 'real-time' and 'AI snipe signal', but does not disclose return format, pagination, or any limitations. For a simple read-only getter, this is adequate but not fully transparent.

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 a single sentence that is front-loaded with the essential action and resource. It includes relevant modifiers (real-time, AI snipe signal) and a cost hint without unnecessary words. No waste.

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 tool with no parameters and no output schema, the description provides the minimal necessary clarity. However, it leaves gaps about what the 'AI snipe signal' means, what fields each launch will contain, and any additional behavior. It is acceptable but not fully complete.

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 has zero parameters, so the description cannot add parameter-specific meaning. Per the rubric, a tool with 0 parameters receives a baseline of 4, and the description appropriately provides context without needing to detail arguments.

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 uses a specific verb ('Get'), names a clear resource ('PumpFun token launches'), and adds unique context ('real-time' and 'AI snipe signal'). This clearly differentiates it from siblings like hyre-token-verdict or hyre-graduating, which likely focus on other aspects.

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 when to use this tool (when you need real-time token launch data with a snipe signal) but does not explicitly mention alternatives or exclusions. It is enough to understand the primary use case but lacks explicit guidance on when not to use it.

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