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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value beyond those by specifying the capped reward amount, per-eligible-participant payout, the zero-payout introduction, and that live funding and automatic payout status are included. This enriches the read-only behavior with concrete expectations.

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 dense sentences cover the main challenge, the referral program, the zero-payout detail, and live status. Information is front-loaded and every clause adds meaning without 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?

For a simple read-only, no-parameter tool with strong safety annotations, the description gives enough context about what will be reported: challenge rules, referral program, funding, and payout status. It could be more explicit about what exact fields or status values are returned, but no output schema exists and the description is sufficient for basic invocation decisions.

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, so there is no parameter semantics burden. The description instead clarifies what information is covered (challenge, referral program, funding, payout status), which is appropriate for a parameter-less informational read.

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 the tool reads the Speedbot Bootstrap Challenge and paid-agent referral program, with a specific verb ('Read') and concrete resource. It conveys the scope and key terms, but it does not explicitly differentiate itself from closely related siblings like speedbot_referral_program or speedbot_start_earning.

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 tool is for viewing earning opportunity details and payout status, but it gives no explicit guidance on when to choose it over alternatives such as speedbot_referral_program, speedbot_info, or speedbot_start_earning. No exclusions or routing criteria are provided.

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