environmental_rights_query

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

No annotations provided, so description bears full burden. It fails to disclose behavior (e.g., read-only, returns information, demo limitations). 'DEMO' is ambiguous but suggests possible non-production status; no concrete details.

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?

Extremely concise at one sentence, but lacks structure and fails to convey essential information. Conciseness here trades off against clarity and completeness.

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 single parameter, no annotations, and existence of an output schema (unseen), the description should explain functionality, input meaning, and output nature. It does not; 'DEMO' suggests incompleteness.

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?

Input schema has one parameter 'topic' with no description (0% schema description coverage). The description does not explain what the topic should be (e.g., format, allowed values), leaving the agent without guidance on valid inputs.

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?

Description states 'Environmental rights under Kenya Constitution 2010 Article 42' but lacks an active verb describing the tool's action. The addition of 'DEMO' further obscures purpose, making it unclear whether this is a functional query tool or a placeholder.

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 on when to use this tool compared to siblings (climate_adaptation_guide, climate_data_guide, conservation_areas, nema_permit_guide). The description does not indicate specific contexts or alternatives.

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