get_health_indicators

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

No annotations provided, so description carries full burden. Discloses conditional behavior based on parameter, fuzzy-matching, and dynamic nature of available indicators. Does not mention rate limits or error handling, but core behavior is well explained.

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?

Two sentences, highly concise. First sentence states purpose and source; second explains usage modes. No redundancy, every word earns its place.

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 low complexity (1 optional parameter, output schema exists), description covers source, behavior, and a caveat about dynamic list. No gaps evident.

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 baseline is 3. Description adds value by specifying 'fuzzy-match' and 'browse-discovered' (not hardcoded), which are not in schema description. Provides useful context beyond schema.

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?

Clearly states tool retrieves National health indicators from PSA OpenSTAT. Distinguishes from siblings focusing on other domains (earthquakes, weather, etc.). Specifies verb 'get' and resource 'health indicators'.

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?

Describes two usage modes: no argument returns default headline set; passing indicator fuzzy-matches. Warns that available list is browse-discovered. Lacks explicit exclusions or comparisons to alternatives, but context from sibling tools implies domain-specific use.

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