Workplace Wellness Guide

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

With no annotations, the description carries the full burden of behavioral disclosure, but it says nothing about whether this is a read-only lookup, what output shape to expect, or any limitations. The term 'Guide' suggests informational content and likely no side effects, but this is left to inference.

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 extremely brief and front-loaded with the core topic. The 'DEMO' suffix adds a minor note about its nature, but it is not entirely necessary for tool selection. Overall it is concise but not a model of structural richness.

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 simple schema and one optional parameter, the bar is low, yet the description still fails to explain how to invoke the tool responsibly—notably how to use the query parameter and what kind of answer an agent can expect. The topic alone is insufficient for confident invocation.

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 single optional 'query' parameter has 0% schema description coverage, and the tool description never references it. There is no hint about what kind of query is expected (topic, keyword, location) or whether it is even needed to retrieve the guide, so an agent cannot confidently set a useful value.

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 identifies the domain as 'Kenya workplace mental health policies and EAP programs,' which distinguishes it from sibling tools like crisis_line_directory or provider_finder. However, it lacks an explicit verb stating what the tool actually does (e.g., 'provides,' 'searches,' 'searches for'), so the purpose is implied rather than explicit.

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 offers no guidance on when to use this tool instead of the listed siblings, nor any exclusions or preferred query scenarios. The only extra signal, 'DEMO,' is ambiguous and does not convey usage context.

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