charity_sector_health

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does indicate the tool is a read-only 'Returns' operation and lists data sources (ATO/ACNC), but it omits potential caveats like data freshness, update frequency, or any limitations on the aggregates. The transparency is adequate but not rich.

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 three sentences long, with the core purpose stated in the first sentence and supporting details (data points, sources, use cases) following. Every sentence earns its place; there is no fluff or repetition of schema information. The structure is efficient and front-loaded.

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?

Given the tool has no parameters, no annotations, and no output schema, the description must explain what the tool returns. It does a good job listing the key data points and the overall purpose, but it does not describe the shape of the response (e.g., JSON structure, units, formatting). For a zero-parameter read-only tool, this is mostly complete.

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 has zero parameters, and the schema confirms this with an empty object. Since there are no parameters to describe, the description does not need to add parameter-level semantics; the baseline of 4 applies. The description does not mention the absence of parameters, but that is unnecessary.

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 ('Returns') and a clear resource ('AU charity sector health snapshot'), followed by a list of the aggregates returned (total active charities, revenue, donations, employment, deltas). This makes the tool's function unambiguous and distinguishes it from sibling tools like 'health' or 'sectoral_employment_shift' which focus on different domains.

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 states a clear use case: 'Single call answers how is the AU not-for-profit sector tracking?' and identifies target audiences (philanthropy, NFP-policy, grant-funder). While it provides strong context for when to use the tool, it does not explicitly mention any exclusions or alternative tools.

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