get_nomenclature_info

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.