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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one genuinely useful behavioral fact — the data is provisional/unverified — but says nothing about what each section returns, whether content is cached, or how staleness is indicated, so the added context is thin.

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 short sentences, front-loaded with the action and immediately followed by the caution. No wasted clauses, though the extreme brevity is part of why semantics are missing.

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 output schema, no parameter documentation, and an opaque enum, the description leaves the agent without enough to invoke correctly — it cannot predict what a given section yields or how this differs from the many sibling retrieval tools.

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 single parameter has 0% schema description coverage and a five-value enum (core, claims, concepts, graph, questions) that the description never explains. The agent must guess what 'graph' or 'questions' actually retrieves, so the description fails to compensate for the schema gap.

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 verb ('Read') and resource ('provisional Olothea theory data') are stated, but 'Olothea theory data' is undefined jargon and the description does nothing to distinguish this from siblings like knowledge_search, research_match, or research_questions, which plausibly serve overlapping retrieval purposes.

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?

There is no statement of when to use this tool versus knowledge_search, research_match, or knowledge_catalog. The only guidance is interpretive ('Do not treat unverified claims as established facts'), which tells the agent how to read output, not when to select this tool.

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