Maternity Paternity Rights

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. 'DEMO' hints that this may be illustrative or limited, but the description does not explain what the tool does, what it returns, or how the query affects behavior.

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, but this is under-specification rather than effective conciseness. The 'DEMO' tag is cryptic and the description lacks enough substance to earn a higher score.

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 optional parameter and an output schema, the definition still omits essential context: how to use the query parameter, what kind of output to expect, and what 'DEMO' implies about reliability or scope. An agent would be guessing at the tool's contract.

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, 'query', is not described at all, and schema description coverage is 0%. The description does not indicate whether the query is a natural-language question, a search term, or optional free text.

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 names a specific topic, 'Kenya maternity and paternity leave rights', which distinguishes it from siblings like minimum_wage_lookup and unfair_dismissal_guide. However, it is a noun phrase rather than a clear verb+resource statement, so it does not explicitly say what action the tool performs.

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 about when to use this tool versus sibling tools. There are no scenarios, exclusions, or alternative recommendations, leaving the agent to infer usage solely from the topic keyword 'Kenya'.

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