get_patient_info

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

With no annotations, the description carries the full burden. It does disclose the return shape ('Returns a dict with keys: fullName, title, contacts, identity'), which is useful. However, it omits access requirements, error behavior, and whether fields may be missing or null, so transparency is incomplete.

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?

Two lean sentences: the first states purpose and scope, the second lists the return keys. Every sentence carries information and no filler is present.

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 parameterless read of a profile, the description documents the returned fields directly, compensating for the lack of an output schema. Minor gaps remain around usage selection and behavioral caveats, but the tool's simplicity keeps these from being critical.

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 zero parameters and full schema coverage, which is the baseline case for 0 params. The description adds no parameter detail because none is required; the schema already communicates that no arguments are needed.

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 states a specific verb ('Get') and a specific resource ('basic patient profile information') and enumerates its contents (name, contacts, identity numbers). That is clear and implicitly distinguishes it from siblings like get_clinical_document or list_invoices, though it does not explicitly call out any sibling.

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 guidance is provided on when to use this tool instead of an alternative. The word 'basic' implies a scope limitation, but no exclusions or conditions are stated, leaving the agent without criteria for tool selection.

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