energy_find_energy_cities

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the data source (ch.bfe.energiestaedte) and the requirement that exactly one of name or location be used. No contradiction with annotations.

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 concise and immediately understandable. The use of structured tags (use_case, important_notes, example) adds value without redundancy, and every sentence serves a 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?

For a read-only search tool with a rich schema and clear annotations, the description covers the core purpose, use context, critical constraint, and example. The output schema presumably documents return values, so no further explanation is needed.

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 input schema already provides detailed descriptions for all parameters. The description goes beyond by reinforcing the mutual exclusivity of name vs. lat/lon and offers a concrete example with sample values, which helps the agent construct valid invocations.

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 uses a specific verb 'Sucht' (searches) and a clear resource: municipalities with the 'Energiestadt' label. It distinguishes itself from sibling tools by targeting municipalities rather than power plants or wind turbines.

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 provides a concrete use case (comparing municipal energy policy) and an important constraint (either name or lat/lon must be provided). It does not explicitly mention alternatives among the sibling tools, but the use case and condition make appropriate usage clear.

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