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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the API-key requirement (auth needs), the 100-row cap, and a polling cadence constraint. It stops short of noting failure behavior, so not quite a 5.

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?

Front-loads the auth requirement and the resource, then moves to field semantics and operational rules in tight sentences. The 'expired' handling sentence is the longest and is arguably verbose, but it earns its place by telling the agent exactly what to do with a common outcome.

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?

With no input parameters and no output schema, the description carries the full burden and meets it: it names every returned field, decodes each status value (available, expired, under_review), and adds polling and auth guidance. Nothing needed to call it correctly 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?

The tool takes zero parameters, so per the baseline there is nothing parameter-level to document; the description instead spends its words on the returned fields and status semantics, which supports correct invocation.

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 (list) plus the resource (USDT deposit requests) and the exact scope (100 most recent), then enumerates the returned fields (status, amount_to_send, amount_received, credited_at). An agent can immediately distinguish this from siblings like lunium_request_usdt_deposit or lunium_get_usdt_wallet.

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?

Gives operational guidance (poll at most every 30-60 seconds) and tells the agent how to advise a user when a deposit is 'expired' or 'under_review', which is useful. However, it never states when to reach for this tool versus alternatives such as lunium_request_usdt_deposit or lunium_get_usdt_wallet; usage is only implied.

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