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

With no annotations, the description carries the full burden and does well: it declares the tool is free and unauthenticated (no credentials or side effects) and defines the edge case that unknown npubs return as not-banned rather than erroring. It stops short of stating latency/rate behavior or that it is a pure read, but the essential behavioral traits are covered.

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 purpose is front-loaded in the first sentence, followed by the lookup semantics, then auth cost, then usage context. Every line earns its place with no redundancy.

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?

An output schema exists, so return values need not be described, and the auth/edge-case behavior is covered. The main remaining gap is the absence of any negative/permission note beyond "free, unauthenticated" for a tool with no annotations.

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?

Only one parameter, and the schema has 0% description coverage, so the schema adds nothing. The description compensates partially by explaining what an unknown npub yields, but it never defines what an npub is or its format (hex vs bech32).

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 and resource ("Check whether an npub is banned") and pins the scope to one community registry, which cleanly separates it from the broader lookup_member and from ban-action siblings like cast_ban_vote and initiate_ban_election. The added rule that unknown npubs are not banned makes the semantics unambiguous.

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 a concrete usage context: "Used by operators during the cold path (credit purchases) to enforce community bans." That is a clear when-to-use, but no explicit when-not or named alternative (e.g. lookup_member for general member data) is offered.

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