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

Annotations declare readOnlyHint=true, so the read-only nature is already known. The description adds significant behavioral context beyond that: it returns the consent split into titled sections, must be presented verbatim, includes version/effective date/content/confirmation prompt/withdrawal instructions, lists available consent types, and notes authentication requirements. It also clarifies the prerequisite for calling consent_submit, which helps the agent understand the operational context. 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 moderately long but every sentence adds value: it states the purpose, mandates verbatim presentation, lists content elements, enumerates consent types, and gives a workflow constraint. It is structured with clear sentences, front-loading the core purpose before elaborating. No unnecessary 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?

The tool returns structured consent text and there is an output schema (indicated by the context signal), so explaining return values is not necessary. The description covers the key contextual aspects: what the returned data contains, how it should be used (verbatim presentation), what consent types are available, and the workflow prerequisite for consent_submit. Authentication is also mentioned. This is sufficiently complete for an agent to use the tool 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 description coverage is 100%, so both consent_id and bearer_token are already described in the schema. The description does not add parameter-level details beyond the schema. The mention of available consent types might help the agent understand what consent_id refers to, but since consent_id is an opaque ID from consent_list, the description does not materially enhance parameter understanding. Baseline 3 is appropriate due to high schema coverage.

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 'Fetch the full text of a specific consent document for patient review,' which is a specific verb+resource. It distinguishes itself from siblings like consent_list (which lists IDs), consent_status (checks status), and consent_submit (submits confirmation). The explicit mention of returning sections and the verbatim presentation requirement further clarifies its unique role.

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 provides explicit usage context: it should be used to fetch consent text for patient review, and the agent must present it verbatim. It also states a workflow rule: the patient must confirm each consent before calling consent_submit, which helps the agent sequence tools correctly. It does not explicitly state 'when not to use,' but the alternative is implied by the sibling list and the mention of consent_submit.

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