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

The description discloses that the action imports content into the patient's chart (write operation), that the response remains after linking (non-destructive), and that routing depends on 'origem'. This adds value beyond the annotations, which are minimal. There is 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 concise, well-structured with bullet points and a clear hierarchy. It is front-loaded with the main purpose, and every sentence contributes value: action explanation, routing, UI reference, tip, and bulk support. No redundant information.

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 description covers the tool's purpose, behavior, and usage tips adequately. It lacks details on error conditions or prerequisites (e.g., response existence), but given the surrounding tools and absence of output schema, it is sufficiently complete for an agent to use 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?

With 0% schema coverage, the description adds meaning by mentioning bulk support via 'patient_ids' and 'response_ids'. However, it does not individually describe each parameter, leaving some ambiguity despite self-explanatory names. The description partially compensates but is not exhaustive.

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 links a pre-consultation response to an existing patient, with specific verb 'Vincular (link)' and resource 'pre-consultation response to patient'. It explains the routing based on 'origem' and provides context that distinguishes it from siblings like webdiet_preconsulta_delete.

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 gives clear context: it is the API-equivalent of the panel button and provides a tip for patient matching when names differ. However, it does not explicitly state when not to use it or mention alternatives, though the context implies that linking is appropriate after obtaining a response via list_responses.

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