Mental Health Rights

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the topic, not what the tool does (e.g., returns a summary, provides legal text, or offers guidance). The word 'DEMO' hints it may be a demonstration but does not clarify expected behavior, side effects, or data handling.

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, which could be seen as concise, but it is under-specified. It lacks essential information about functionality and parameters. It is not structured to front-load key details; it simply states the topic without elaboration.

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?

Although an output schema exists and the tool has only one optional parameter, the description is too sparse to allow an agent to invoke it correctly. It does not explain what output is produced, how the topic parameter influences it, or what the tool returns. The presence of an output schema does not compensate for the absence of usage context.

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%, and the description does not mention the 'topic' parameter at all. There is no explanation of how this optional parameter affects results or what values are expected. The description fails to compensate for the schema's lack of parameter documentation.

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 identifies the subject: mental health rights under a specific act (Kenya Mental Health Act 2022). It distinguishes itself from sibling tools like provider finder or crisis directory by focusing on rights rather than services. However, it lacks an explicit verb (e.g., 'get', 'list', 'explain'), so it reads more as a title than an action statement.

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?

There is no guidance on when to use this tool versus the siblings. No mention of appropriate contexts, exclusions, or conditions. The description implies a user seeking rights information, but provides no explicit direction or alternatives.

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