list_pending_exams

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

No annotations are provided, so the description must carry behavioral context. It conveys a read-only listing action and the filtering semantics, but it does not describe edge cases, ordering, grouping, or what 'pending' means in terms of status transitions. Still, the basic behavior is neither misleading nor 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?

A single sentence that is concise, front-loaded, and contains no filler. It efficiently communicates both the primary action and the optional filters.

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?

For a simple read-only listing tool with two optional parameters and an output schema, the description is largely adequate. It does not define 'pending' precisely or specify ordering/grouping, but the core invocation logic is complete enough to act on.

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. It successfully gives meaning to both parameters: 'medical_record' corresponds to 'every patient or one medical record', and 'overdue_only' is explained as 'optionally overdue only'. It does not give format details, but the semantic coverage is strong for a two-parameter tool.

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 verb 'List' and the resource 'pending exams', and specifies the two scoping options: every patient or a single medical record, plus the optional overdue-only filter. This distinguishes it from sibling tools that record, schedule, or compare lab results.

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 offers a clear context for use: retrieving pending exams, with a clear choice between all patients and one record. It does not explicitly name alternatives or exclusion conditions, but the scope is clear enough for an agent to decide when to invoke it.

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