find_schools_nearby

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the default radius, optional filtering, and the exact return structure (name, distance, education levels, contact info). It omits error handling and permission details, but for a read-only search tool, the described behavior is sufficiently transparent.

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 appropriately sized and well-structured. It leads with a one-line summary, adds a brief context paragraph, then provides cleanly formatted Args and Returns sections. Every sentence earns its place, and the information is front-loaded for quick scanning.

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?

For a 4-parameter tool with no annotations and no output schema, the description is remarkably complete. It covers the tool's purpose, target use case, all parameters with formats and defaults, and the return structure. Nothing essential is missing for an agent to invoke it correctly.

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?

Despite 0% schema description coverage, the description explains every parameter in detail: latitude and longitude as decimal degrees, radius in meters with a default, and education_levels as an optional list with concrete examples. This fully compensates for the schema's lack of descriptions and adds crucial semantic meaning.

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 opens with 'Locate educational institutions near a specific location, filtered by education level' — a specific verb with a resource and constraints. It clearly distinguishes itself from generic siblings like find_nearby_places by focusing exclusively on schools and educational institutions.

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 positions the tool as a 'specialized search tool' and explicitly states its value for 'families evaluating neighborhoods or real estate purchases', giving strong usage context. It does not explicitly name alternatives or state when not to use it, but the niche is so well-defined that the guidance is effectively clear.

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