search_medical_concepts

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

With no annotations, the description carries the behavioral disclosure burden. It does state the search behavior and return type ('Returns matching SNOMED CT concepts'), which is helpful. However, it does not explicitly say the operation is read-only or describe any limitations, pagination, or match semantics.

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?

A single, front-loaded sentence conveys the search action, the fields searched, and the expected result type with no wasted words. It gives the agent necessary context quickly.

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 tool with one parameter and no output schema, the description is quite complete: it names searchable fields, the result target (SNOMED CT concepts), and the domain restriction. A minor gap is not describing the exact structure of the returned concepts, but the tool complexity is low.

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?

The schema already documents the one parameter with examples, and schema description coverage is 100%, so the baseline is 3. The description adds meaningful beyond-schema nuance by stating the query matches both 'name or description', clarifying how the search behaves.

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 clear action ('Search for medical concepts') and resource, with a specific scope ('SNOMED CT concepts for dermatology conditions'). It is distinct in function, but does not explicitly differentiate from sibling tools like search_medical_info or lookup_medical_concept, so it misses the top tier.

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 description implies when to use the tool: when you need to find medical concepts by name or description. It does not mention exclusions or alternative tools, so an agent is left to infer when this is preferred over the many sibling search/lookup tools.

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