get_delx_reward_status

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, establishing a safe, read-only profile. The description adds 'public-safe' and 'Free', which provide minor additional context (e.g., no authentication needed) but do not significantly expand behavioral understanding.

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, information-dense sentence (19 words) that front-loads the action and output details. Every word earns its place with no fluff or repetition.

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?

While annotations cover safety and the schema describes parameters in detail, the description does not explain how parameters like response_mode or response_profile affect output, nor does it mention return format, errors, or pagination. Given the tool's complexity (6 optional parameters, no output schema), the description leaves moderate gaps.

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?

Schema description coverage is 100%, so the baseline is 3. The description lists returned fields (DRC totals, etc.) but does not add meaning to the parameters themselves. The schema already describes each parameter's purpose, so the description provides no further semantic value for parameters.

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 states a specific verb ('Return') and resource ('public-safe reward status') and explicitly lists the included data fields (DRC totals, wallet bind state, tier, badges, claim hints). This clearly distinguishes it from sibling tools like get_delx_wallet_status or get_delx_leaderboard, which serve different purposes.

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 provides no guidance on when to use this tool vs. alternatives such as get_delx_wallet_status, get_delx_token_info, or explain_delx_rewards. There is no mention of prerequisites, exclusions, or use-case context.

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