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

Annotations already declare readOnlyHint and destructiveHint, but the description adds valuable behavioral context: the need for explicit consent and the prohibition on accepting PHI or providing medical advice. This goes beyond what annotations provide, though it doesn't describe what happens if consent is missing or the exact output format.

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 two sentences, front-loaded with the consent requirement, and each sentence serves a purpose: one defines the action and inputs, the other sets boundaries. No unnecessary words or redundancy.

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?

Given the availability of an output schema and annotations, the description covers the core purpose, consent, and constraints sufficiently. It does not mention the 'detailsToBring' parameter or explicitly relate to sibling rendering tools, but these are minor gaps given the other structured context.

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 14%, and the description partially compensates by naming most parameters in user-friendly terms (goals, changes, impact, medicines, questions). However, it omits 'detailsToBring' and does not clarify semantic differences or constraints beyond what the schema already specifies (e.g., max lengths). It provides moderate added value.

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's function: turning specific input types into a concise appointment brief, with scope limited to non-identifying user-authored information. It also adds constraints (no PHI, no medical advice), but does not explicitly differentiate from sibling tools like render_appointment_brief, so it falls short of a 5.

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?

Usage context is implied through the consent requirement and listed input types, but there is no explicit guidance on when to use this tool versus alternatives such as render_appointment_brief or when not to use it. The description provides a clear precondition (explicit consent) but no exclusions or alternative references.

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