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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it lists the specific consent documents, notes the return fields (IDs, titles, summaries, order), and emphasizes that each consent must be fetched individually. It also mentions authentication, which is relevant for a patient-session tool. No contradiction with 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?

The description is well-structured and front-loaded: the first sentence states the core purpose, followed by return values, a helpful enumerated list of consent types, and a workflow note. Every sentence adds useful information, and there is no fluff or repetition.

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 tool's moderate complexity and the presence of an output schema, the description is complete. It explains what the tool returns, the required consents, and the necessary workflow (fetch each via consent_text, confirm). It also notes the read-only nature implicitly through 'list' and explicitly via the annotation, making it well-rounded.

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 the baseline is 3. The description does not add extra meaning to the parameters beyond what the schema provides (intake_id and bearer_token). It mentions authentication, but that is already explicit in the bearer_token parameter description.

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 purpose: 'Get the list of all consent documents a patient must accept before ordering medication.' It specifies the resource (consent documents), the action (list), and the context (before ordering medication). It also distinguishes from sibling tools like consent_text (fetch individual consent) and consent_submit (confirm consent) by focusing on listing required consents.

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?

The description explicitly provides usage guidance: 'Each consent must be fetched individually via consent_text and confirmed by the patient before proceeding.' This names the alternative tool (consent_text) and clarifies the workflow order. It also implies that consent_list is the first step, not a replacement for fetching text or confirming.

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