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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by framing it as a one-time comprehensive guide whose contents are fuller than the connector instructions, though it does not describe return format or length.

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 is two sentences and front-loads the main purpose before listing the guide's coverage. The list earns its place by telling the agent what practical material the guide contains, and the second sentence adds the key invocation rule without fluff.

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 zero-parameter, read-only guide with no output schema, the description provides enough context: it states what the guide covers and when to invoke it. There is no output-schema richness requiring explanation, and the annotations already cover safety/idempotency.

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 has zero parameters, so there are no parameter semantics to explain. Per the baseline for parameterless tools, this is adequately handled without needing description content.

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 identifies the tool as the complete research method and archive guide, then enumerates its contents (periodicals, decade-by-decade coverage, period vocabulary, OCR issues, places, dates, people, recipes). It also signals scope by saying it is for the start of a research task rather than single-line verification, though it does not explicitly name the sibling tools it differs from.

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?

It gives explicit usage timing: call it once at the beginning of every research task that is not a single-line verification. That provides a clear when-to-use and a when-not-to-use boundary, but it does not name specific alternative sibling tools such as verify_quote or archive_info.

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