request_immunization_resource

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

With no annotations, the description carries the full burden and does disclose key behaviors: it performs mutating CRUD operations, requires confirmation for deletes, forbids auto-filling data, and mandates app links in the response. However, it lacks details on authentication, error handling, or permission requirements, so it's not fully 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?

The description is reasonably concise and well-structured: a clear opening, a bulleted list of rules, and an Args/Returns section. The rules are valuable but add length, so it doesn't achieve a perfect 5.

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 the essential CRUD operation flow and return type, and includes important deletion confirmation. However, it omits how to handle the nested 'request' parameter correctly and doesn't discuss error responses, status codes, or pagination, leaving gaps for a CRUD tool.

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 explains method, path, and body with an example path, adding some value beyond the schema. However, it presents these as top-level args while the schema wraps them in a single 'request' object, which could confuse an agent. This mismatch means the description only partially compensates for the schema's minimal descriptions.

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 specifically targets the FHIR Immunization resource with CRUD operations. This separates it from sibling tools that handle other resource types, such as request_patient_resource or request_observation_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 scopes usage to the Immunization resource and provides important behavioral rules: using only user-provided data, not guessing missing data, asking for confirmation before deletion, and providing app (not API) links. While it doesn't directly mention alternatives, the resource-specific scope makes the appropriate tool choice clear.

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