request_condition_resource

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

With no annotations, the description carries the full burden. It discloses important behaviors: use only user-provided data, do not auto-fill, ask confirmation for delete, and provide app links rather than API links. These go beyond basic CRUD semantics and help the agent act safely.

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?

Well structured with an intro, bulleted rules, and Args/Returns sections. The content is relevant, though the Returns line is somewhat redundant with the intro. Overall, concise and easy to scan.

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?

Provides useful CRUD rules and examples, but misses key context like the base URL expectation, error handling, and the nested request wrapper. As a generic FHIR request tool with no output schema, more details about invocation structure and edge cases are needed.

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 lists method, path, and body, but the actual schema expects a single 'request' object wrapping these fields. This structural mismatch could cause incorrect invocation. Schema description coverage is 0%, so the description needed to clarify the wrapper but did not.

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 for CRUD operations specifically on the Condition resource, using a specific verb and resource. It distinguishes from sibling tools by restricting scope to Condition.

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 'only on the FHIR Condition resource', providing a clear when-not-to-use for other resources. It also gives contextual rules for create/update/delete (e.g., confirmation for deletion). Does not name alternative tools explicitly, but the scope restriction is effective.

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