get_classification_info

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

With no annotations, the description carries the behavioral burden and does reasonably well: 'Read' establishes a non-mutating operation with no side effects, and it explicitly describes what is returned (structured explanatory text about organization, browsing, and ranks). It stops short of noting that the page is static/argument-free or anything about size or caching, but for a zero-parameter info tool the disclosure is solid.

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, no waste, and the action is front-loaded before the return-content detail. Each clause ('how prokaryotes are organized', 'how to browse taxa by rank', 'what taxonomic ranks are used') earns its place.

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 simple, zero-parameter, read-only info tool with no output schema, the description adequately covers what the tool is and what it returns. The only meaningful omission is disambiguation from the sibling get_classification.

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 per the rubric the baseline is 4. The description adds no parameter detail because none is needed or possible.

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 gives a specific verb + resource: 'Read the navigation and classification information page from LPSN', which is clearly distinct from data-query tools like search_taxa or get_taxon_detail. However, it does not differentiate itself from the very similarly named sibling get_classification, so an agent could conflate the two without opening the 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?

Usage is only implied: the content described ('how prokaryotes are organized, how to browse taxa by rank') suggests this is orientation material to consult before browsing. There is no explicit when-to-use/when-not statement and no routing away from get_classification or get_text_page, which are plausible alternatives.

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