Find castles near a point

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

No annotations provided, so description alone covers behavior. Mentions default radius (100 km), max (2000), nearest-first ordering, and distance_km inclusion. Lacks info on auth, rate limits, empty result handling, or pagination. Adequate but gaps remain.

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, zero waste. First sentence conveys core purpose and output. Second sentence provides usage guidance. Purpose is front-loaded.

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?

No output schema; description states distance_km included but other result fields unspecified. With 5 parameters and moderate complexity, covers essentials but lacks result format 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 40% (limit and radius described in schema). Description adds radius default and max, plus geocoding hint. Latitude, longitude, and category lack parameter-level description beyond schema min/max/enum. Modest value added.

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 'List landmarks within a radius of a WGS84 coordinate, nearest first, each with distance_km.' Verb 'list' and specific resource 'landmarks' (castles) with clear scope. Distinguishes from siblings like 'search_castles' (generic search) and 'top_castles' (non-geographic).

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?

Explicitly advises geocoding place first then calling with lat/lng. Implies when-not-to-use (e.g., for single castle use get_castle), but does not explicitly exclude alternatives.

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