wxoGetMedicalInformation

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the return content and the possibility of 'None', but lacks detail on error handling, permissions, or output structure. The behavior is minimally transparent.

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 sentence and fairly concise, but contains a typo ('inforamation') and awkward phrasing ('or None'). It is not fully polished but avoids unnecessary words.

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 one-param tool with an output schema, the description gives a basic overview of what is returned. However, it does not explain when 'None' is returned, nor does it address potential errors or access considerations. Adequate but with clear gaps.

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 coverage is 0%, so the description should compensate, but it says nothing about the patient_id parameter. The parameter name is inferable, but no format, validation, or meaning is provided beyond the 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 clearly states the tool returns comprehensive patient medical information covering diagnosis, allergies, and prescriptions, which distinguishes it from sibling tools like vital signs or drug information. However, the phrase 'or None' is slightly ambiguous, and 'comprehensive' is vague.

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?

No explicit guidance is given on when to use this tool versus siblings like wxoGetPatientInformation or wxoGetVitalSignsInformation. The context is implied by the description, but no exclusions or alternatives are mentioned.

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