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

No annotations are provided, so the description carries the full burden. It discloses the authentication requirement (OAuth or kc_ member key), per-connection scoping, daily quota pooling, and that only the caller's own account is reflected. It does not explicitly claim read-only behavior, but the zero-parameter schema and 'tells you' phrasing strongly imply a side-effect-free read.

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 opens with a bold, one-line summary of the tool's output, then expands with exactly the details an agent needs: the quota pool, uncapping for DB reads, the personal scope, and authentication methods. No sentence is redundant; it is appropriately sized for a zero-parameter tool.

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 tool with no parameters and an output schema present, the description covers all needed behavioral context: what data is returned, how it is scoped, and how to be recognized as a member. The only minor omission is explicit error behavior for unauthenticated calls, but the sign-in instruction implies that.

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 accepts zero parameters, so there is no parameter semantics to document. Schema description coverage is 100% by definition, and the description adds useful meaning about what the returned data represents: membership tier, quota used, and uncapped DB reads. The zero-parameter baseline is 4.

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 states the tool's purpose: it returns the authenticated account's membership tier and today's live-fetch quota. It explicitly scopes the result to 'YOUR account' and excludes 'global / operator data', distinguishing it from the sibling data tools.

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 description implies when to use the tool: it reports the shared daily pull pool used by real-time search, view refresh, debate, and x-sentiment, and notes that DB-read tools are uncapped. It tells the agent that quota checks are relevant for live-fetch operations, but it does not explicitly name alternatives or provide a direct 'use this when' statement.

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