her_count_features

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

No annotations provided, so description carries full burden. Discloses it is fast, returns counts by designation type, and explains parameters. However, it does not mention potential limits on area size or count, nor pagination behavior. Still, it provides sufficient behavioral context for typical use.

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?

Concise and well-structured: a title line, brief paragraph, then Args and Returns sections, plus tips. Every sentence adds value with no redundancy. Front-loaded with purpose.

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?

All 3 parameters are described, return value is explained (counts by designation type), and performance tip is given. No output schema, but description covers what is needed. Given simplicity, it is complete.

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 is 0%, but description compensates by explaining each parameter: designation_type filter semantics, bbox format in BNG, output_mode options. Adds meaning beyond type definitions.

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?

Clearly states the tool counts heritage features in an area and returns counts by designation type. Distinguishes from search tools by emphasizing it doesn't fetch full records. The verb 'count' and resource 'heritage features' are specific, and it differentiates from sibling her_search_designations.

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 to use this before her_search_designations to estimate result sizes, providing clear when-to-use guidance. Also suggests using it to decide whether to narrow search area. Sibling tool is named, giving actionable context.

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