labor_rights_query

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

With no annotations, the description carries the transparency burden. It discloses that results are a DEMO summary and not legal advice, which is a key behavioral limitation. It also implies read-only via 'Query.' It does not add further details like output format or rate limits, but for a simple query tool this is adequate and adds value beyond the schema.

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, front-loaded sentence with no filler. Every part adds value: the verb, the resource (Kenya Employment Act 2007), the parameter guidance (by topic with examples), and the disclaimer.

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?

The tool is simple (one parameter) and has an output schema, so the description need not elaborate on return values. The description covers purpose, parameter hints, and a key limitation. It feels complete for a demo-level query tool, though it could optionally mention which specific topics are covered more precisely.

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 provides no description or enums for the 'topic' parameter, so the description compensates by listing example topics: 'maternity, overtime, termination, etc.' This gives the agent a clear sense of acceptable values, though it does not define exhaustive options or formatting.

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's function: 'Query Kenya Employment Act 2007 rights by topic' with specific verb and resource. It distinguishes itself from sibling tools by focusing on legal rights topics (maternity, overtime, termination), which is unique among the listed tools.

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?

The description implies usage for querying labor rights by topic and includes an important caveat: 'DEMO summary — not legal advice.' However, it does not explicitly contrast with alternative tools or state when not to use it beyond the legal disclaimer, so guidance is partially implied rather than explicit.

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