lookup_procedure

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention that the tool is read-only, any authentication requirements, or the nature of the output (e.g., what information is returned). This is insufficient for safe agent invocation.

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?

The description is a single sentence with no superfluous words. It is front-loaded with the action and resource. Every part earns its place.

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?

Despite having no output schema and sparse annotations, the description does not explain what the tool returns (e.g., full MedlinePlus entry, summary, links) or any limitations (e.g., rate limiting, required codes). A lookup tool with only input specs is incomplete for effective agent use.

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 input schema provides descriptions for 3 of 4 parameters (75% coverage). The description adds context about MedlinePlus and code systems but does not elaborate on parameter semantics beyond what the schema states. No additional format or syntax guidance.

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 the action ('Look up'), the resource ('MedlinePlus information'), and the specific input types ('CPT or SNOMED CT procedure codes'). It distinguishes itself from sibling tools (lookup_medication, lookup_diagnosis, etc.) by focusing on procedure codes.

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 usage for procedure code lookups via the input schema and mentions of CPT/SNOMED CT. However, it lacks explicit guidance on when to use this tool over siblings or specific prerequisites (e.g., requiring an authenticated session).

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