her_count_aerial

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

Discloses that the tool is fast, returns a count, and no geometry. Lacks details on error handling or authentication, but for a simple count tool, the transparency is good.

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?

Well-structured with clear sections (Args, Returns, Tips). Every sentence is informative and concise without redundancy.

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 4 parameters, no output schema, and no annotations, the description thoroughly explains the tool's purpose, parameter details, and usage scenario. The inclusion of a usage tip enhances completeness.

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?

With 0% schema description coverage, the description fully compensates by specifying format for bbox (BNG coordinates), example values for monument_type and period, and options for output_mode. This adds crucial meaning beyond the bare schema.

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 counts aerial mapping features in an area, emphasizes speed and no geometry return, and distinguishes itself from her_search_aerial by specifying the result is a count.

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 using this tool before her_search_aerial to gauge result size, providing clear when-to-use guidance. Also includes a tip for LLMs to call it before fetching full records.

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