ecitizen_guide

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

No annotations are provided. The description only says 'DEMO' which hints at limited functionality but does not explain behavioral traits such as read-only nature, rate limits, or whether it returns static or live data. The description fails to disclose what happens when the tool is invoked.

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 short (one sentence) but lacks essential information. 'DEMO' is an unnecessary qualifier. It is under-specified rather than concisely informative.

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 presence of an output schema, the description should explain what the guide returns (e.g., text, links, steps). It does not. The tool is simple (one param) but still incomplete; the agent cannot use it 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?

Schema description coverage is 0%. The description does not explain the single parameter 'service_category' at all. The agent has no idea what values to provide or how it affects the output.

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 says 'Guide to Kenya eCitizen portal services' which indicates a guidance role but is vague. The addition of 'DEMO' suggests it is not a functional tool, yet the purpose is unclear. It does not differentiate from sibling tools like huduma_centre_guide.

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 such as form_checklist or huduma_centre_guide. No context about prerequisites or typical use cases.

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