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

Annotations declare readOnly, idempotent, non-destructive. The description adds that it returns the newest 50 actions newest first, which is useful behavioral context beyond annotations (result limit and ordering). It doesn't describe pagination beyond the fixed 50, keeping it below 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?

It's a single long run-on sentence with no strong front-loading; the key items are present but the phrasing is dense and somewhat hard to parse. It earns most of its content but lacks structure.

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?

No output schema exists, so the description appropriately enumerates the returned fields and the 50-item ordering. Combined with readOnly annotations, an agent has enough to call it and understand what comes back.

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?

One optional parameter ('key') with 100% schema description coverage that already documents the fallback-auth behavior. The description adds no param details, so 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?

The description enumerates the resources returned: ARTI balance, welcome tab remainder, daily stipend/freeroll eligibility and rule, and the user's newest 50 actions. It's a clear read-oriented account summary. It doesn't distinguish from siblings like 'limits' or 'links', but the content scope is specific.

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 guidance on when to use this vs alternatives like 'limits' or by sibling tools. Usage is implied by the content description (use it to see your balance/history). Minimum viable.

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