literacy_resources

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

Annotations declare readOnlyHint=true, which the description does not contradict. The description adds no behavioral details beyond those annotations, such as data freshness, authentication needs, or that it is a demo. The DEMO tag is noted but not a behavioral trait.

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 with clear subject matter. It is concise and front-loaded. However, it could be better structured with a verb and optional usage hints.

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 simplicity of the tool (2 optional params) and existence of an output schema, the description does not explain the output context or any constraints like which counties are covered. The DEMO label suggests incomplete data but is not elaborated.

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 50%: county has a description, age_group does not. The tool description mentions no parameters or their meanings, so it adds no value beyond the schema. For the undocumented age_group parameter, a description would help.

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 clearly states the tool provides information about adult education, literacy programs, and continuing education in Kenya. It distinguishes from siblings like school_finder and tvet_programs which focus on other education levels. However, it lacks a verb like 'list' or 'search', making the action implicit.

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. The description does not mention prerequisites, exclusions, or recommended contexts. The DEMO label suggests caution but is not actionable.

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