list_patients

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the core behavior (searching by conditions and returning id list + summary) but does not address potential caveats such as default behavior when filters are absent, pagination, authentication, or rate limits. This is a moderate level of transparency for a read-oriented list operation.

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, well-structured sentence that immediately conveys the action, target, criteria, and output. Every word earns its place, with no redundant information.

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?

An output schema exists, so the description need not detail return values. However, given the open-ended 'filter' object and lack of annotations, the description could provide more context on filter structure, pagination, or ordering. It is minimally sufficient but leaves several operational aspects unspecified.

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 partially explains the 'filter' parameter by listing example attributes (age band, stage, dialysis modality), but it does not explain the 'caller' parameter or specify how the filter object should be structured. This leaves significant ambiguity for the agent.

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 tool's purpose: to search a pediatric patient cohort ('检索患儿队列') using criteria such as age band, stage, and dialysis modality, and to return a list of IDs with summaries. This distinguishes it from sibling tools that fetch individual profiles or perform verifications.

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 provides clear context: use this tool when you need to retrieve a cohort of patients based on specific conditions like age band, stage, or dialysis modality. It does not explicitly mention alternatives or exclusion cases, but the context is clear enough for an agent to decide when to use it.

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