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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint: false, so the safety profile is covered. The description aligns with annotations and adds useful context like live funding, automatic payout status, and the intro-paying-0 caveat, but it does not disclose return format or other behavioral details beyond that.

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 compact and front-loads the main purpose. However, 'Includes live funding' partially duplicates the earlier 'live wallet-funded', and 'The introduction pays 0' is terse enough to be ambiguous. Still, it remains efficiently scannable for an agent.

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, read-only tool with no output schema and strong annotations, the description covers what the tool reads and the key reward terms. It does not define 'introduction pays 0' or describe the exact response structure, but those are minor gaps given the tool's simplicity.

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 and 100% schema description coverage, so there are no parameter semantics for the description to clarify. With 0 params, the baseline of 4 applies.

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 opens with the verb 'Read' and names a specific resource: live wallet-funded Speedbot Bootstrap rewards, including concrete terms like 1 USDC per eligible participant and the separate paid-agent referral program. It is clear what the tool surfaces, though it does not explicitly distinguish itself from sibling tools such as speedbot_start_earning or speedbot_referral_program.

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 this is the read-only tool for viewing earning opportunities, but it gives no explicit when-to-use or when-not-to-use guidance and names no alternative tools. An agent must infer when this is the right choice versus related earning, referral, or work-finding siblings.

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