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

Annotations already declare readOnlyHint=true, so the safety profile is clear. The description adds useful behavioral context by specifying the fuzzy-tolerance behavior and the underlying RxNav endpoint, though it does not describe return structure, ranking, or error behavior.

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 compact sentences front-load the core matching behavior and then provide the REST endpoint. There is no filler or repetition.

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?

The tool is simple, all three parameters are documented in the schema, and annotations cover read-only safety. The description is nearly complete for invocation, though it could say more about what candidates or identifiers are returned since no output schema exists.

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 schema already explains term, option, and maxEntries, including an example and enum meanings. The description adds no further parameter semantics beyond what the schema provides.

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 names a specific operation ('Fuzzy match') and resource ('RxNorm names'), and clarifies the matching tolerance for abbreviations, misspellings, and extra words. It distinguishes itself implicitly from exact-name lookup siblings, but does not explicitly name an alternative tool.

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 fuzzy-matching scope implies when this tool is appropriate, especially versus exact name lookup, but there is no explicit guidance on when to prefer it over siblings like rxnorm_find_rxcui_by_name or rxnorm_get_spelling_suggestions.

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