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

readOnlyHint=true already establishes this is a safe read, so the description's remaining burden is low. It adds that this maps to RxNav GET /rxcui/{rxcui}/property and hints at the returned shape (category, name, value), but says nothing about behavior for unknown property names or concepts.

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 operation and its examples, then the underlying REST route. Nothing is wasted, though the endpoint reference is marginally useful only to a caller that cares about the wire mapping.

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?

With no output schema, the description partly compensates by naming the returned tuple (category, name, value). But it omits the key disambiguation against the near-identically named plural sibling, leaving an agent to guess which of the two to call.

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 both parameters are already documented in the schema, including the 'ATC' / 'RxNorm Synonym' examples. The description restates those same examples (ATC code, synonym) without adding new semantics such as accepted property-name vocabulary or case sensitivity.

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 a named property of a concept) and gives concrete examples (ATC code, synonym), so the operation is unambiguous. However, it does not distinguish itself from the sibling rxnorm_get_concept_properties (plural), which by name sounds like the same capability.

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 statement of when to use this tool versus rxnorm_get_concept_properties, rxnorm_get_all_related, or other sibling lookups. The RxNav endpoint reference implies a single-property retrieval, but the description never tells the agent when a single-property fetch is preferred over the bulk properties call.

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