request_medication_resource

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

With no annotations, the description carries full responsibility. It discloses CRUD behavior, data handling rules (no guessing/auto-filling), the need for deletion confirmation, and the requirement to return app links. It also states the response format (JSON).

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 purpose statement, rules, Args, and Returns sections. It avoids unnecessary verbosity while including all critical information. A slight length increase is justified by the operational rules.

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 tool has an output schema, and the description explains the JSON response. It covers essential behaviors like CRUD scope, deletion confirmation, and link requirements. It could mention authentication or error handling, but for a FHIR resource client this is sufficiently 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?

The description provides an Args section that clearly explains method, path, and body, including examples like '/Medication?code=aspirin'. Since schema description coverage is 0%, this is essential and adds meaningful context 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 the tool performs HTTP requests for CRUD operations exclusively on the FHIR Medication resource. This differentiates it from sibling resource-specific tools like request_patient_resource and request_generic_resource.

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?

It explicitly says to use this tool for CRUD operations only on the Medication resource, which provides clear scope. It also provides rules for creating/updating (use only user data) and deleting (ask confirmation). However, it does not explicitly mention alternatives for non-Medication resources.

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