list_patients_above_age

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

With no annotations present, the description carries the full burden. It discloses that the operation is a read-only 'list', clarifies the strict greater-than semantics, and describes the return behavior including the empty case. It stops short of mentioning potential details like ordering or pagination, but these are not necessary for such a simple tool.

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 compact and well-structured: a one-sentence purpose, an Args section for the parameter, and a Returns section. Every sentence earns its place with no redundancy or fluff.

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?

Despite having no output schema, the description covers the essential behavior: what the tool does, what the parameter means, and what is returned. The tool's simplicity means no further context is needed, and the sibling list does not introduce missing requirements.

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 schema descriptions coverage is 0%, so the description must compensate. It does so thoroughly by explaining the 'age' parameter as 'the age threshold' and explicitly stating that it returns patients older than this number. This adds meaningful semantic context beyond the raw 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 starts with a specific verb ('List') and a resource ('patients') with a clear filtering condition ('age is strictly greater than the given value'). This directly distinguishes it from sibling tools like get_patient_by_id or find_patients_by_disease, which target different criteria.

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 clearly implies the use case: when you need to retrieve patients above a certain age threshold. It provides context without explicitly naming alternatives, but the unique filtering criterion makes the intended usage obvious. It does not include any exclusions, hence a 4 rather than a 5.

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