request_medication_resource

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals critical behaviors: not auto-filling missing data during create/update, requiring user confirmation before deletion, and returning app links instead of API links. These are non-obvious behaviors that an agent must know to invoke the tool safely and correctly.

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 well-structured with a clear opening statement, a rules list, and an Args section. It is slightly longer than necessary but every sentence provides value, and the formatting improves scannability.

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?

The description covers purpose, usage rules, parameter semantics, and return type. It lacks explicit error-handling or edge-case information, but given that an output schema exists and the tool is straightforward CRUD, it is sufficiently complete for an agent to invoke it correctly in most scenarios.

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?

Although the input schema contains descriptions, the context signal reports 0% schema description coverage. The description compensates by providing an Args section with examples for path ('/Medication', '/Medication?code=aspirin') and clarifying that body is optional for POST/PUT. This adds practical meaning beyond the schema's bare definitions.

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 makes HTTP requests to the FHIR server and explicitly limits usage to CRUD operations on the Medication resource. This differentiates it from sibling resource-specific tools such as request_patient_resource, making the purpose unmistakable.

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 explicitly says 'Use this tool to perform CRUD operations only on the FHIR Medication resource,' which is a direct usage directive. It also provides conditional rules: do not guess data for create/update, ask for confirmation before delete, and provide app links in responses. These guidelines clearly indicate when and how to use the tool.

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