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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: the program is terminated, so the agent should expect historical/status data and no actionable payout, which prevents it from being invoked in the hope of earning.

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 short sentences, no filler, and the most decision-relevant fact (the reward program has ended) is front-loaded before the description of what is returned.

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 single-optional-parameter read tool with full annotations and no output schema, the description adequately covers what the call yields (historical eligibility plus current status) and why it is safe to call. It could be slightly more complete by stating what the returned status values mean, but nothing essential to correct invocation is missing.

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?

There is only one parameter (agent_key) and schema description coverage is 100%, including its format, sourcing from speedbot_register, and the Authorization bearer alternative. The description adds nothing about the parameter, so the baseline 3 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?

States a specific verb (read) and resource (historical eligibility and current status of the service-listing reward program), which is more than a restatement of the name. It does not explicitly name a sibling, but the 'no new reward is offered' clause separates it from claim/award tools like speedbot_exchange_award or speedbot_claim_dot_bonus.

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 'rewards have ended' and 'no new reward is offered' framing implicitly tells the agent this is a read-only historical lookup and not a way to claim anything, which is a partial when-not signal. However, it never names an alternative tool or states a positive trigger condition ('call this when you need to verify past eligibility for ...'), leaving usage to inference.

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