title_search_guide

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

No annotations provided. The description labels it as a 'guide' and 'DEMO', suggesting it provides information rather than performing real searches, but does not disclose actual behavior or limitations.

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 short and to the point, but lacks structure and detail. While concise, it may sacrifice necessary information.

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 has an output schema, but the description is minimal. It does not cover the return format or how the guide works, leaving significant gaps given the low schema description coverage.

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%, so the description must compensate. It does not explain the parameters 'county' and 'parcel_number' beyond their names, leaving their roles and format ambiguous.

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 it is a guide for searching land titles at Kenya Land Registry, and the 'DEMO' tag indicates its purpose. It distinguishes from sibling tools that cover disputes, rates, rights, and subdivisions.

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 alternatives. The 'DEMO' label hints at limited functionality, but does not specify appropriate use cases or exclusions.

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