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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes further by disclosing the consent prerequisite, the transient (non-persistent) processing model, the preservation of supplied fields and disclaimer, and the explicit PHI exclusion — meaningful data-handling context beyond the 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?

Three short sentences, front-loaded with purpose followed by the consent requirement and the scope boundary. Every sentence adds a distinct fact with no filler.

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 values need no explanation, and the consent/PHI behavior is covered. However, with eight required parameters at 13 percent schema coverage, the description leaves most input semantics for the caller to infer from names alone.

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 only 13 percent (only consentConfirmed is documented in the schema), so the description carries most of the burden. It adds scope constraints around disclaimer/consent and PHI, but says nothing about the six content parameters (mainGoal, changes, impacts, medicines, questions, detailsToBring) beyond a generic "preserves the supplied fields."

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 ("renders") and resource ("appointment brief") plus the output form ("accessible card"). The qualifiers "supplied" and "complete" implicitly distinguish it from the sibling prepare_appointment_brief, which would build the brief, though no sibling is named explicitly.

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?

Gives clear preconditions ("supplied, complete, non-identifying" brief plus explicit consent for transient processing), which tells the agent when the tool is applicable. It never names an alternative tool or states when not to use it, so usage is implied rather than routed.

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