health_rights_query

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

With no annotations, the description must disclose behavioral traits. It only states the subject matter and 'DEMO', implying possible incompleteness or test status. It does not confirm read-only nature, required permissions, or other behaviors such as rate limits or data freshness.

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 brief (one sentence plus 'DEMO'), which is concise but loses informational value. It is front-loaded with the core purpose, but fails to provide essential details. Conciseness is not an excuse for under-specification.

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 tool's simplicity (1 param, no annotations, output schema present but not described), the description is incomplete. It lacks parameter explanation, usage examples, and behavioral context. The presence of an output schema does not absolve the need for a richer description.

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%. The description does not explain the 'topic' parameter at all—what values are valid, format, or examples. The parameter is a required string, but the tool adds no semantic value beyond the schema. This is a critical gap for agent understanding.

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 specifies the tool's function: querying patient rights under Kenya Health Act 2017. It provides a clear verb+resource combination. However, the 'DEMO' suffix introduces ambiguity about its operational status, and it does not differentiate from sibling tools, though the context suggests uniqueness.

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 provided on when to use this tool versus alternatives. The description does not indicate appropriate topics for the 'topic' parameter, nor does it mention any prerequisites or limitations. Users must infer usage from the tool name alone.

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