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

readOnlyHint=true already declares this as a safe read, so the bar is lower. The description adds the underlying REST call (GET /rxcui/{rxcui}/property) and the returned property shape (category, name, value), which is useful grounding, but says nothing about auth, lookup failures for unknown property names, or rate limits.

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 tight sentences: the purpose and examples come first, the REST mapping second. Nothing is wasted, though the endpoint reference is supplementary rather than essential for the main decision.

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 2 required params fully documented in the schema, no output schema, and no nesting, the description plus schema is nearly sufficient; it even sketches the return shape (category, name, value). The only real gap is sibling disambiguation against rxnorm_get_concept_properties.

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 (rxcui, propName) are already documented in the schema. The description's 'category, name, value' phrasing describes the return shape of a property rather than adding parameter-level detail, so it does not meaningfully exceed the schema baseline.

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 (a named property of a concept) and gives concrete examples (ATC code, synonym). The phrase 'a named property' implicitly distinguishes it from the sibling rxnorm_get_concept_properties (which returns all), but it never names that sibling 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?

The examples 'ATC code or a synonym' imply when this tool is useful, so usage is inferable. However, there is no explicit when/when-not guidance and no routing to the very close sibling rxnorm_get_concept_properties, which an agent would need to distinguish this from.

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