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

Annotations cover only readOnlyHint=true, so the description carries the rest: it discloses the fields returned per doc and the anti-hallucination constraint. It does not describe ordering, doc count, or whether the listing is complete vs paginated, so it falls short of fully transparent.

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?

Purpose and return shape are front-loaded in the first sentence, followed by usage conditions. The long run-on enumeration of topics (data sources, provider keys, billing, annotations...) is dense but each item maps to a real retrieval scenario, so it is useful rather than filler.

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, no output schema, and only a readOnly annotation, the description must supply both the return contract and the routing logic — and it does both, including the follow-up call. Nothing an agent needs in order to call this correctly is absent.

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 zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter guidance is needed or missing.

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 precise verb and resource — listing every AIdata help doc — and enumerates the exact payload each entry carries (slug, title, summary, section headings). It also names the sibling get-help-doc that consumes the result, so an agent can separate listing from reading without inspecting schemas.

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 explicit trigger conditions: user asks how to do something in AIdata, asks about a platform with no dedicated tool, or a tool fails due to missing setup. It routes the agent onward to get-help-doc and adds a clear prohibition against answering from memory.

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