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

With no annotations supplied, the description carries the disclosure burden and does add real behavioral context: which features refuse on Community, which refuse below Researcher, and that the two Researcher gates raise different exception types. It never explicitly says the call is side-effect free, which is the one gap for a tool with zero annotation coverage.

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?

Two sentences, both loaded with actionable content, and the version-plus-tier purpose is stated first. The 'first three / last two' mapping across the feature list takes a moment to parse but earns its brevity.

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 no explanation, and there are no parameters to cover. What remains absent is an explicit statement that the lookup is a safe read and whether results are stable across versions.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline 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?

It states concretely what the tool returns: the documentation's covered version plus the licence tier required per feature. That is specific enough to separate it from search_docs, list_topics and explain_error, though it does so by implication rather than naming an alternative.

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 when-to-use guidance is unusually explicit: call it before writing code around sweeps, walk-forward, cross-exchange, the GPU or the tick layer. What's missing is any explicit steering toward or away from the sibling tools for adjacent questions.

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