Minimum Wage Lookup

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

With no annotations provided, the description bears the full burden of behavioral disclosure. The 'DEMO' tag hints that the data may be demonstrational or unreliable, but it does not explain what the tool actually returns, whether filtering is exact or partial, or what happens when parameters are omitted. This is too thin to set correct behavioral expectations.

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 two short sentences with no filler. The core purpose ('Kenya minimum wage by sector and county') is front-loaded, and 'DEMO' is a separate useful flag. It is appropriately concise, though the structure is flat and could benefit from explicit usage cues.

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?

For a tool with two optional parameters and no annotation support, the description omits critical operational context: what to do with null parameters, whether data is real or demo-only, and when to prefer this lookup over related guides. The presence of an output schema covers return shape, but query semantics and limitations remain unexplained.

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 schema has 0% description coverage, so the description must add meaning to 'county' and 'sector.' It echoes those exact parameter names ('by sector and county') without explaining allowed values, combination semantics, or defaults. This adds little beyond what the property names already convey.

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 a specific resource ('Kenya minimum wage') and the query dimensions ('by sector and county'), clearly distinguishing it from sibling tools that cover employment rights guides and directories. It lacks an explicit verb like 'lookup' or 'retrieve,' but the noun phrase conveys the purpose unambiguously.

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 given on when to use this tool versus the sibling tools (e.g., unfair_dismissal_guide, maternity_paternity_rights). There is no mention of exclusions, prerequisites, or how to decide between tools. The purpose implies use for wage lookups, but that is left to inference.

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