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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description focuses on data scope: safe metadata, aggregates, and entitlement previews. The explicit 'never returns' clause adds a useful privacy boundary beyond the annotations. No contradiction with the provided 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?

Three sentences front-load the purpose, then list included data and explicit non-goals. The lists are long but each item clarifies scope; there is no filler 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?

With one required parameter, an output schema, and strong read-only annotations, the description has enough information to invoke the tool correctly. The only minor gap is not telling the agent how to resolve a 'known' clinicId, e.g., via list_clinics, though that is inferable from siblings.

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?

The schema already fully documents clinicId with type, pattern, and description (100% coverage). The main description adds only the notion that the clinic must be 'known' (existing), which is mildly useful but not a major semantic expansion.

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 opens with a specific verb ('render') and a bounded resource ('administrative overview for a known DoctoFam clinic'), then enumerates the exact aggregate components included. This makes it easy to distinguish from granular sibling tools like list_providers or get_clinic.

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?

It clearly frames the tool as a high-level administrative overview and explicitly lists what it never returns, ruling out use cases needing clinical details. However, it does not name sibling alternatives or state a direct routing rule such as 'for detailed lists, use list_*.'

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