land_dispute_paths

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

No annotations. The description does not disclose any behavioral traits such as read-only, destructive effects, or authentication needs. 'DEMO' hints at non-production status but is not explicit.

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 short (two words plus 'DEMO'), but this is under-specification rather than conciseness. Every sentence is too minimal to be helpful.

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 has an output schema and 2 parameters, the description is severely incomplete. It lacks parameter explanations, usage context, and behavioral details.

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 coverage is 0%, and the description adds no meaning to the parameters (dispute_type, county). The agent gets no help understanding what values are expected or how parameters affect results.

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 is vague, stating 'Land dispute resolution pathways in Kenya. DEMO.' It does not specify a clear verb (e.g., get, list, find) and 'DEMO' undermines clarity. It minimally clarifies the resource but lacks action.

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 versus siblings like land_rates_query or title_search_guide. The description provides no context for selection.

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