find_nearest_mosques

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

No annotations are provided, so the description must carry full burden. It mentions 'verified mosques' and 'injects map routing navigation strings,' which adds value, but doesn't specify sorting, result handling, or network requirements.

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?

Two sentences with no fluff, front-loaded with the main purpose. The second sentence adds unique value (navigation injection) efficiently.

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 no output schema, no annotations, and 4 parameters with 0% schema coverage, the description is incomplete. It doesn't describe the output format, error handling, or what happens with multiple results.

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 explain parameters like location_name, latitude, longitude, or distance_km in detail. It mentions 'target search radius' but fails to clarify how parameters interact or are required.

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 the tool finds verified mosques, masjids, or suraus within a radius and injects navigation strings for Google Maps and Waze, distinguishing it from sibling tools that handle prayer times and events.

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?

The description implies the tool is for finding nearby mosques, but lacks explicit guidance on when to use it versus alternatives or exclusions. Given sibling tools exist, this could be improved.

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