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

The annotation readOnlyHint=true already tells the agent this is a safe, non-mutating lookup. The description adds no further behavioral detail such as result count limits, ranking behavior, or what happens when no suggestions exist, so it contributes only modest value beyond the structured fields.

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. The trailing 'RxNav REST: GET /spellingsuggestions' is endpoint trivia that does not help an agent decide or invoke the tool, but it costs little.

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-only lookup with no output schema, the definition covers what the tool does and what input it expects. Only the differentiation from the approximate-match sibling is missing, which is a modest gap at this complexity level.

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 schema itself provides both the semantics and a concrete example ('ibuprofin'). The description's restatement of 'possibly-misspelled drug name' adds no syntax or format detail beyond what the schema already gives, so 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 ('Get spelling suggestions for a possibly-misspelled drug name'), which clearly identifies the operation. It does not, however, distinguish itself from the closely related sibling rxnorm_get_approximate_match, leaving the agent to infer the difference.

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 'possibly-misspelled drug name' implies the input condition under which this tool is appropriate, so usage is hinted at. But there is no explicit when/when-not guidance and no mention of the near-synonym sibling rxnorm_get_approximate_match, which is the main selection ambiguity.

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