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

The annotations already declare this as a safe, read-only, idempotent operation. The description adds useful behavioral context by stating that it requires a key and by describing the returned contents: remaining quota and invite statuses. It does not discuss pagination or ordering, but those gaps are minor for a zero-parameter list tool.

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 efficient sentence that front-loads the core resource and includes only relevant scoping and prerequisite details. No sentence is redundant or wasted.

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 parameters, clear annotations, and no output schema, the description supplies the key missing context: authentication requirement and the shape of the returned information. An agent has enough information to select and invoke this tool 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 are no parameters to document, which meets the baseline of 4. The description appropriately does not invent parameter semantics, and the empty schema is fully consistent with the tool description.

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 and what it returns: the key owner's invites, remaining quota, and per-invite status. It does not explicitly name sibling tools such as create_invite or redeem_code, but the read-oriented status listing is distinct enough to avoid confusion.

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 prerequisite 'Needs a key' provides context for when this tool is callable, and the content implies it is for checking existing invites and quota. However, it gives no explicit guidance on when to use this versus create_invite or redeem_code, nor any exclusions.

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