her_capabilities

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

Describes return content (capabilities, LLM guidance) and the output_mode parameter. No annotations provided, but description fully discloses behavior as a read-only listing.

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?

Front-loaded with purpose, followed by details and usage tips. Somewhat verbose with docstring format but every sentence adds value.

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?

Complete for a discovery tool: lists what it returns (sources, tools, queries, spatial references, LLM guidance) and provides usage advice. No output schema needed as return is well-described.

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?

The only parameter 'output_mode' is explained as 'Response format — "json" (default) or "text"', adding meaning beyond the schema which only has a default. With 0% schema coverage, description compensates adequately but is minimal.

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 it lists full server capabilities including sources, tools, and supported queries. Distinguishes from sibling tools like her_search_monuments or her_export_geojson by being a meta tool for discovery.

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 'Call this once at the start of a session' to understand available tools and how to use them effectively, providing clear when-to-use guidance.

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