Self Help Resources

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the resource is and appends 'DEMO.' It does not disclose whether this returns a static list, supports search, has limitations, requires anything, or what the response contains. This is insufficient for an agent to predict tool behavior.

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 brief and front-loaded, which is good for scanning. However, the standalone 'DEMO.' adds little value and the overall text is more under-specified than concise; it saves words by omitting essential behavioral and parameter context.

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 optional 'area' parameter, an output schema, and sibling tools providing some context, the tool is not highly complex. However, the description fails to explain how the 'area' parameter works, what the tool returns, or how this relates to sibling tools, so the agent cannot reliably use it correctly.

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 input schema has one parameter ('area') with 0% schema description coverageache, and the tool description does not mention or explain this parameter. The agent is left to guess whether 'area' is a geographic region, a topic area, or something else, especially given the Kenya-specific context.

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 clear resource ('Kenya mental health self-help resources and support groups'), and the geographic scope helps differentiate from sibling tools like crisis_line_directory or workplace_wellness_guide. However, it lacks an explicit verb indicating what the tool does (list? search? provide?). It is more of a content label than an action-oriented purpose statement.

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?

There is no guidance on when to use this tool versus sibling tools such as mental_health_provider_finder or crisis_line_directory. The context is implied by the resource type, but no exclusions or alternative conditions are stated, leaving the agent to infer which tool fits a given user request.

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