huduma_centre_guide

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

The description says 'Guide' and 'DEMO' but does not disclose behavioral traits such as read-only nature, data source, or limitations. Without annotations, the description carries the full burden but is insufficient.

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 that is too brief to convey essential information. While concise, it sacrifices completeness without earning 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 the single optional parameter and the presence of an output schema, the description does not explain the output or how to use the tool effectively. The 'DEMO' label suggests it's a stub, but the description is far from complete.

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 'county' is not mentioned in the description. With 0% schema description coverage, the description fails to add any meaning beyond the schema, leaving the agent uninformed about the parameter's purpose.

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 'Guide to Kenya Huduma Centre services and locations.' This is a clear verb+resource combination indicating the tool provides guidance. However, it does not distinguish from sibling tool 'ecitizen_guide' which might serve a similar purpose for eCitizen 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?

No guidance is provided on when to use this tool versus alternatives like ecitizen_guide or the form-related tools. There is no mention of prerequisites or context.

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