wxoGetPatientInformation

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

The description adds the behavioral detail that the tool returns 'or None,' indicating a possible absence of data. It also specifies the scope of information returned. However, there is no mention of permissions, security, or error behavior, which is a notable gap given the healthcare context and lack of annotations.

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, front-loaded sentence that conveys the core function and key exception return value without redundancy. Every word earns its place.

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?

Given the tool's simplicity (one parameter, read-like operation) and the existence of an output schema, the description adequately covers the essential aspects: what it returns and the None case. It does not need to detail return structure since the output schema handles that.

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 has one parameter, patient_id, with 0% description coverage. The description does not explain the parameter's purpose or format beyond what the schema already provides, so it adds no value to parameter understanding.

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 function: 'Returns basic patient information from the healthcare database.' It lists specific data categories (personal details, contact information, insurance data), which distinguishes it from sibling tools focused on drugs or vitals.

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?

Usage is implied by listing the type of data returned; when a user needs basic patient info, this tool is appropriate. However, it does not explicitly mention when to use it over alternatives, nor does it state exclusions or prerequisites.

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