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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by flagging the payload as PHI (a sensitivity/compliance consideration) and exposing the underlying Elation endpoint. It still omits auth requirements and rate limits, so it stops short of a 5.

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 tight sentences with the core purpose and payload fields front-loaded, followed by the endpoint as a terse reference. No filler. The endpoint fragment is slightly cryptic but costs almost nothing.

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?

With a fully described 5-parameter schema and complete annotations, the remaining gap was return values, and the description lists the problem fields (including ICD-9/10/SNOMED and status values), covering that in the absence of an output schema. Pagination mechanics are left entirely to the schema, which is acceptable but not ideal.

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 100%, so limit, cursor, offset, status, and patient are all documented in the schema itself. The description's mention of status values (Active, Controlled, Resolved) merely restates the enum and adds no syntax or semantic detail beyond it; baseline 3 applies.

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?

States a specific verb ('List') and resource ('one patient's problem list') and enumerates the returned fields (description, ICD codes, status, dates, synopsis). This clearly separates it from sibling list tools such as list_allergies, list_medications, and list_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?

Scope ('one patient's problem list') implies the usage context, and the endpoint hint (GET /problems/?patient=) reinforces it, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives for problem data. The required patient id source is documented only in the schema, not the description.

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