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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond that: the data is private ('shown to you alone'), restricted to members, split by UTC day/week/month, and includes pending changes.

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 front-loaded sentence with no wasted phrases. The privacy constraint and membership requirement are stated up front, followed by the returned information breakdown.

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 simple read-only tool with no output schema, the description does the necessary work by enumerating the returned values (limits, losses, remaining, reset timing, pending changes) and stating the privacy/membership context. An agent has enough information to call it correctly.

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 optional parameter, and the schema already gives it 100% description coverage including the fallback authentication use case. The tool description adds no parameter-specific meaning, so the baseline of 3 is appropriate.

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 clearly identifies the resource (your own loss limits and cool-off) and what it returns (daily/weekly/monthly limits, losses so far, remaining allowance, reset timing, pending changes). It implicitly distinguishes viewing from mutation, but does not explicitly name or differentiate from sibling `set_limits`.

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?

It says the tool is 'for members' and shows your own limits, which implies a view/read context, but gives no explicit when-to-use guidance or alternatives. It never says to use `set_limits` to request changes or explains when this tool should be preferred over `history`.

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