schedule_lab_exam

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and a date format hint, without disclosing side effects, whether the schedule can be modified, required permissions, or what the response indicates. This is a scheduling/mutation operation, and the behavior is largely opaque.

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 short sentence with no filler words, and the core action is front-loaded. However, the phrasing 'YYYY-MM-DD order and due dates' is confusing and poorly structured, and the sentence omits important context that would make it genuinely useful.

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?

With five required parameters, zero schema descriptions, no annotations, and an output schema that the description does not illuminate, this description is not complete enough. It lacks parameter explanations, behavioral details, and usage context. While it is a relatively simple scheduling action, the agent is left with major gaps in how to call the tool correctly.

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?

Schema description coverage is 0%, so the description must compensate for the five undocumented string parameters. It only hints that ordered_at and due_date should use YYYY-MM-DD format, but gives no meaning for medical_record, test_code, or test_name. This is insufficient for an agent to construct a correct invocation.

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 names a specific verb and resource ('Schedule a laboratory exam'), which clearly identifies the tool's core action. However, the phrase 'using YYYY-MM-DD order and due dates' is awkwardly worded and could confuse an agent, and it does not explicitly differentiate from the sibling tools that also relate to lab exams.

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?

There is no guidance on when to use this tool versus siblings like record_lab_result or list_pending_exams. The date format hint is a formatting instruction, not a usage context. An agent receives no information about prerequisites, exclusions, or alternative tools.

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