lookup_diagnosis

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('look up') and resource ('MedlinePlus health-topic links'), but does not disclose what happens if the code is not found, any rate limits, or the structure of the returned links. It is minimally transparent.

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, well-formed sentence that conveys the core purpose without extraneous words. It is front-loaded with the action and specific code systems, making it efficient for quick scanning.

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?

Given the absence of an output schema, the description could be more explicit about the return format (e.g., list of links, titles). However, for a straightforward lookup tool, the mention of 'health-topic links' provides sufficient context for an agent to understand the general outcome. It is reasonably complete.

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 75%, meaning the schema already documents most parameters well. The description adds context that the 'codeSystem' parameter includes ICD-10-CM, ICD-9-CM, or SNOMED CT, which aligns with the schema enum. However, it does not significantly enhance understanding beyond the schema.

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?

The description clearly states it looks up MedlinePlus health-topic links for diagnosis codes, specifying three code systems (ICD-10-CM, ICD-9-CM, SNOMED CT). This distinguishes it from sibling tools like lookup_medication or lookup_lab_test, which target different medical entities.

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?

While no explicit 'when to use' or 'when not to use' guidance is given, the tool name and description make it obvious that it is intended for diagnosis codes. The context of sibling tools implies alternative tools for medications, labs, procedures, and general MedlinePlus connections, providing indirect usage context.

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