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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the shape of the response (aliases, category, hierarchy, paper count), which signals a read-only, non-destructive lookup, but it says nothing about behavior when the ID is unknown, whether IDs are normalized, or any rate/permission considerations.

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?

A single front-loaded sentence with no filler; the verb, scope, and returned fields all appear immediately. Nothing is redundant or padded.

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?

An output schema exists, so the description need not explain return values, and for a one-parameter read tool the description is close to adequate. The key gap is the concept_id contract — its format and provenance — which is the main thing an agent could get wrong when calling this 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?

There is one required parameter, concept_id, with 0% schema description coverage, so the description must supply the missing meaning. It never states the expected identifier format (e.g., an internal concept key vs. a namespaced ID) or whether the ID must come from search_concepts, leaving the sole parameter effectively undocumented.

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 uses a specific verb and resource ("Get one standardized concept") and scopes it to a single record, which implicitly contrasts with search_concepts. It also enumerates the payload (aliases, category, hierarchy, paper count). It stops short of naming a sibling or stating the distinguishing condition 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 only implied: the phrase "one standardized concept" suggests a direct lookup by ID rather than a search, so an agent can infer this is the fetch-by-identifier path. There is no explicit when-to-use statement, no mention of search_concepts as the alternative, and no note about prerequisites such as needing a valid concept ID.

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