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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is lighter. It adds that the underlying call is a REST GET and lists the six fields returned, which is useful since no output schema exists, but it says nothing about error behavior for invalid RxCUIs or whether results can be empty.

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 what is returned, then the endpoint mapping. Every clause carries information, though the raw REST path is arguably redundant for an MCP caller.

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 annotations covering safety and no output schema, the enumerated return fields are the key missing piece and they are present. What is absent is disambiguation from the similarly named sibling, which is the main completeness gap.

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 rxcui parameter is fully documented in the schema, so baseline 3 applies. The description only echoes the parameter implicitly via the URL template and adds no format or validity constraints beyond the schema's example.

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 (Get) and resource (RxNorm properties of a concept) and enumerates the returned fields (name, synonym, tty, language, suppress, umlscui). It does not, however, distinguish itself from the near-identically named sibling rxnorm_get_property, leaving an agent to guess which to call.

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 guidance, no prerequisite (e.g. you must already hold an RxCUI), and no mention of when to prefer this over rxnorm_get_property or rxnorm_get_all_related. Usage must be inferred entirely from the name.

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