chw_service_lookup

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

No annotations provided, so description carries full burden. It indicates a read operation ('lookup') but adds no details about response format, pagination, or limitations. 'DEMO' hints at restricted functionality but is vague.

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 very short (one sentence, 7 words), which is concise but includes the unnecessary 'DEMO' tag. It is not structured with bullet points or sections, but the brevity is acceptable for a simple tool.

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?

Despite having only one parameter and an output schema, the description lacks details about what CHW services are, the scope (e.g., which sub-counties are supported), and the output structure. The 'DEMO' label suggests limitations not explained.

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 0%. Description does not explain the 'sub_county' parameter, such as expected format (e.g., exact name, code) or examples. This leaves the agent with no guidance on how to populate the parameter.

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?

Description clearly states the tool 'Lookup CHW services in a Kenya sub-county', specifying the action (lookup), resource (CHW services), and location (Kenya sub-county). The mention of 'DEMO' slightly detracts. Does not explicitly distinguish from siblings, but the resource is unique enough.

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?

No guidance on when to use this tool versus alternatives like health_facility_finder. No mention of when-not-to-use or prerequisites. The description is a single statement with no contextual hints.

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