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

Adds substantial context beyond the readOnly/idempotent annotations: language mirroring, the refusal/routing behavior for emergencies and prognosis, the PII restriction, and the educational-not-medical-advice stance. Annotations cover safety profile; this description covers the semantic and ethical behavior an agent needs.

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?

Front-loaded with purpose and grounding, then coverage, then output shape and safety carve-outs. Slightly dense with the long topical enumeration, but every clause adds routing or behavioral value.

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 return-value enumeration beyond the brief mention is unnecessary. The description nonetheless anticipates the key behavioral edge cases (refusals, PII, educational framing) an agent needs to invoke this correctly.

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 100% with each parameter's description covering purpose, format, and the no-identifier constraint. The description only restates the 'no personal identifiers' rule and language behavior, which the schema already documents, so it adds little beyond baseline.

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 (answers), a specific resource (cancer patient/caregiver questions), and the grounding sources (NCCN Guidelines, medical literature). It enumerates concrete topical coverage that distinguishes it from the trial/feedback/case siblings.

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?

Explicitly names when NOT to use the answer path: emergencies, prognosis/life-expectancy, and pediatric questions route to a safety message and the care team. The topical list also implies when to reach for this tool versus siblings like find_clinical_trials.

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