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

No annotations are provided, so the description carries the full behavioral burden. It discloses that it returns a list of all taxa at a rank (implying potentially very large result sets), but says nothing about read-only safety, pagination, ordering, result caps, or rate limits.

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 tight sentences, front-loaded with the primary action and scope, with the optional filter trailing. The enumerated rank list is somewhat redundant with the schema enum but serves as a quick reference.

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 two-parameter read tool with no output schema and no annotations, the description covers both parameters and the kind of result. It is still missing scale/pagination or result-limit guidance, which matters given 'all taxa' at ranks like domain.

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?

Schema description coverage is 100%, so the baseline is 3. The description restates the rank values and mentions the optional letter filter, which is redundant with the schema; notably its parenthetical rank list omits 'kingdom', which the schema enum includes.

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 specific verb (browse) and resource (all taxa at a given taxonomic rank on LPSN), and scopes it precisely with the rank enumeration. It is distinguishable from search_taxa and get_taxon_detail, though it does not name those siblings explicitly.

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 implied: use this when you want to enumerate taxa at a rank rather than look up a specific one. There is no explicit when-to-use statement, no mention of when search_taxa would be preferable, and no prerequisites stated.

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

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

With no annotations, the description carries the full burden. It does disclose the data source and mechanism ('Walks up the parent chain on LPSN'), which is useful behavioral context, but says nothing about failure behavior for an unresolved name, lookup cost, or result shape beyond the lineage span. Adequate for a low-risk read tool, but 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 core action and followed by the scope detail. No filler, no redundancy.

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 and no annotations, the description does well to sketch the return value ('complete taxonomic classification... from domain down to the target taxon') and the data source. The notable gap is disambiguation from the similarly named sibling tools, which an agent needs in order to select correctly.

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?

Schema description coverage is 100% for the single parameter, which already documents that it accepts either a full LPSN taxon URL or a scientific name. The description adds only the 'prokaryotic name' constraint, which the schema does not state, so it is a marginal addition over the structured field.

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 specific verb and resource ('Get the complete taxonomic classification (lineage)') and bounds the scope ('from domain down to the target taxon', 'for a prokaryotic name'). However, it does nothing to distinguish itself from the near-identically named sibling get_classification_info or from get_taxon_detail, so an agent must still guess which one to pick.

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 when-to-use or when-not-to-use guidance and no named alternative, despite a sibling (get_classification_info) whose name is almost indistinguishable from this one. The only implicit cue is 'for a prokaryotic name', which limits scope but does not route between tools.

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

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.

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

With no annotations, the description carries the full burden: it signals a read-only operation ('Read') and discloses the return shape ('Returns structured text'), which is useful. However, it says nothing about authentication, rate limits, or whether the page is static or versioned, leaving the behavioral profile thin for a no-annotation tool.

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 filler, with the resource and the return content front-loaded. Every clause earns its place and an agent can parse intent at a glance.

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 tool with no output schema, the description adequately covers what the tool does and what it returns. The only minor gap is the absence of any routing hint against get_text_page, which is a small omission given the tool's simplicity.

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 parameter semantics are trivially satisfied; the baseline for 0-parameter tools is 4. Nothing in the description misrepresents the call signature.

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 states a specific verb ('Read') and resource ('the nomenclature rules and guidelines page from LPSN') and clarifies the content domain (ICNP rules for prokaryotic nomenclature). It does not explicitly differentiate itself from the potentially overlapping sibling get_text_page, which could also fetch text pages, so it falls short of a 5.

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 content domain (nomenclature rules) implies when an agent would want this page versus taxonomic lookups, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the competing get_text_page sibling. Usage is inferred rather than stated.

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

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

With no annotations, the description carries the full burden; it discloses the data source (LPSN) and the two accepted input forms, and implies a read-only retrieval. It does not say what happens for an unknown or ambiguous name (error vs. suggestions), whether the lookup is exact-match, or any rate/latency characteristics.

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 filler: the capability and its content coverage come first, the input constraint follows. Nothing is redundant enough to remove.

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 single-parameter read tool with no output schema and no annotations, enumerating the returned fields largely substitutes for a return-value spec. The remaining gap is failure/ambiguity behavior when a name does not resolve uniquely.

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?

Schema description coverage is 100% for the single name_or_url parameter, so the schema already documents both accepted forms and supplies the 'Escherichia coli' example. The description's sentence about name-or-URL restates the schema rather than adding format or validation detail, so the baseline 3 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?

States a specific verb and resource ('Retrieve detailed information about a specific prokaryotic taxon from LPSN') and enumerates the returned content (etymology, type strain, status, synonyms, basonyms, parent/child taxa, notes, references), which distinguishes it from narrower siblings like get_classification or get_nomenclature_info. It never names those siblings, so the differentiation is implicit rather than explicit.

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 only guidance is 'Provide either a scientific name or a full LPSN URL,' which is input formatting, not when-to-use. There is no statement of when to prefer this over search_taxa, get_classification_info, or get_text_page, and no prerequisites or exclusion conditions.

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

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a non-mutating fetch, but the description says nothing about authentication, error behavior for an invalid path, response format, or rate limits.

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 purpose followed by concrete examples. No filler and nothing that fails to earn 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?

There is no output schema and no annotations, so the description is the only source of behavioral and return information. It covers what the tool fetches but leaves the returned content format and failure modes unspecified, which is a gap for an unannotated tool.

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?

Schema description coverage is 100% and the single 'path' parameter is already documented with example values. The description's own examples merely echo the schema, adding no syntax or constraint detail beyond it, so the baseline of 3 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?

States a specific verb ('Read') and resource ('informational text page from the LPSN website'), which clearly separates it from the taxa-oriented siblings. It stops short of explicitly naming a sibling or drawing the boundary against them, so it is clear but not fully differentiated.

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 phrase 'Useful for pages like text/nomenclature, text/navigation, text/etymology, text/faq' implies the intended use cases, giving more than nothing. However there is no explicit when-to-use vs when-not, no mention of alternatives for retrieving this content, and no prerequisites.

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

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

With no annotations, the description carries the full burden. It usefully discloses the return shape (matching names with rank, status, and LPSN URL) and existence of fuzzy matching, but says nothing about permissions, rate limits, pagination, or how many results are returned.

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?

Three short sentences, front-loaded with the core action and followed by return values and usage. The trailing bare URL is largely redundant given the return-value sentence already mentions LPSN URLs, but overall very little waste.

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 low-complexity, read-only two-parameter search with no output schema, the description covers what the tool does and what it returns. It is adequate, though it lacks result-count, pagination, or ambiguity-handling details an agent might need.

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?

Schema description coverage is 100%, with both query and exact fully documented in-schema, so the schema does the heavy lifting. The description's "scientific name or partial name" phrasing only restates the query parameter without adding format constraints or examples beyond the schema.

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 and resource: search the LPSN database for prokaryotic names (bacteria and archaea), returning names with rank, status, and URL. That is clearly distinct from get_taxon_detail or browse_by_rank in spirit, but no sibling tool is named explicitly, so it stops short of the top mark.

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?

"Use this tool to find taxa by scientific name or partial name" states a use case, but gives no when-not-to-use guidance and never points to get_taxon_detail or browse_by_rank as the follow-up or alternative path. Usage is implied rather than fully directed.

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