community_welfare_guide

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

No annotations are provided, so the description must explain behavioral traits. It does not disclose whether the tool is read-only, has side effects, or if 'DEMO' implies limits. The description is insufficient for an agent to infer 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 a single sentence plus 'DEMO', very concise and front-loaded. However, it is too brief to be fully informative; the word 'DEMO' suggests it may not be production-ready.

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 output schema exists, the description should explain what the tool returns. It does not. The parameter 'need' is left unexplained, making the tool incomplete for an agent to use effectively.

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 only parameter 'need' has zero schema description coverage and no explanation in the tool description. The description does not clarify its purpose, expected values, or how to use it.

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 states the tool is about accessing Kenya religious community welfare programs, indicating purpose. However, it lacks specificity on what action the tool performs (e.g., retrieving a guide) and does not distinguish it from sibling tools like catholic_diocese_finder or religious_community_services.

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 explicit guidance on when to use this tool versus its siblings. The description only says 'How to access...', but does not clarify if it should be used for general inquiries or specific denominations.

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