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

Goes well beyond the read-only annotations: it discloses the result cardinality (up to 3 guides), the return fields (title, link, most relevant passage), and an operational instruction for handling panel_url. It also notes the corpus is Brazilian Portuguese while English keywords still work, which the agent cannot know from structured data.

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?

Front-loaded with the primary action and scope, and every sentence carries information (scope, return shape, link handling, escalation). The parenthetical about language and the long topic list make it slightly dense, but nothing is wasted.

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?

With no output schema, the description supplies the return shape and the field-level action for panel_url, and it handles the escalation path. An agent has everything needed to call it and to act on the result.

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 coverage is 100%, so the baseline is 3; the description raises it by explaining that English keywords are acceptable in addition to Portuguese and by reinforcing the task-oriented query style. It stops short of guidance on query phrasing or multi-concept queries.

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 and resource ("Search the All4Clinic help center") and enumerates the domains covered (scheduling, patients, medical records, finance, inventory, etc.), so an agent can match an intent to this tool immediately. It also names the sibling it is not (read_help_article) for the full-guide case.

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?

Explicit invocation context ("for how to do something in the system") plus a clear routing rule to read_help_article when the snippet is not enough. It does not distinguish the other sibling lookup tools (get_faq, list_help_topics), leaving that boundary to inference.

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