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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), so the bar is lower. The description adds the substantive part those annotations cannot: the exact content domains returned (offerings, non-offerings, payment model, languages, intake), which matters because there is no output schema. It does not disclose whether the data is static or how fresh it is.

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 entity and purpose are front-loaded in the first clause, followed by a compact content list and a one-line usage rule. It is a single dense sentence plus a short imperative, with no filler, though the mid-sentence enumeration is list-heavy.

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 parameters and no output schema, the description correctly carries the burden of describing what comes back, and it enumerates the content domains plus the routing rule. What is missing is minor: freshness/static-vs-live nature of the overview and whether it links to the more specific sibling tools.

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 tool takes zero parameters, which is the baseline-4 case; there is nothing to disambiguate. The description's topic list does not need to map to arguments and does not create schema confusion.

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 names a concrete resource (Facts about Foundations Counseling LLC) and enumerates its scope — offerings, exclusions, payment model, languages, intake. It is clearly distinguishable from narrow siblings like get_fees_and_insurance or get_locations, though it never names those siblings explicitly, so differentiation stays implicit.

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?

"Use this first for general questions about the practice" gives a clear routing rule and implies the narrow siblings handle the specific topics it only summarizes. It stops short of naming an alternative or stating when-not to use it, so it is clear context rather than a full when/when-not/alternatives treatment.

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