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

Annotations only establish readOnlyHint; the description adds meaningful context beyond that: the data is private, covers eligibility as well as balance, and the credits are internal at a founder-declared accounting rate with no cash redemption or market trading. That prevents the agent from treating the number as real money. It does not describe the return shape or auth requirements.

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 tightly written sentences with no filler. The core action is front-loaded and the value-semantics caveat follows immediately.

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, the description conveys what is retrieved (balance and eligibility) and the semantic constraints on the returned credits. It leaves auth/privacy preconditions and return formatting implicit, which is a minor gap given the low complexity.

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 this dimension is scored 4. There is nothing for the description to disambiguate at the input level.

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?

Specific verb and resource: read LUMINIS balance and eligibility, with a clear read-only scope. It does not name or contrast any sibling tool (e.g. eclypse_account), and LUMINIS is left as an undefined domain term, so differentiation relies on prior knowledge.

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?

No explicit when-to-use statement and no named alternatives despite ten sibling tools. The only boundary offered ('no cash redemption or market trading') limits interpretation of the value rather than telling the agent when to call this versus another tool.

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