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

Annotations already declare the operation as read-only, idempotent and open-world, so the safety profile is covered. The description adds useful behavioral detail: the outcome values, matching device data, alternatives, and importantly the caveat that the separate datasheet object is not checked by Synergrid and is not part of the approval.

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 front-loaded with the core purpose and then layers in return behavior, a caveat, and an example. It is generally well structured and avoids obvious waste, though it includes return-value detail that the output schema already covers.

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 four-parameter lookup tool with an output schema and read-only annotations, the description supplies the key context an agent needs: what is checked, what is returned, and the important datasheet limitation. Its main omission is explicit routing guidance against sibling tools.

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 description coverage is 100%, so the input schema already documents all four parameters. The description adds a useful example of the required query format, but it does not meaningfully expand on the semantics of locale, phases or smaxVa beyond what the schema provides.

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 states a specific verb and resource: checking whether a PV inverter, battery inverter or PGU is on the Synergrid C10/26 homologation list. It is very clear what the tool does, but it does not explicitly differentiate itself from siblings such as suggest_inverter_c10_26 or get_inverter_datasheet.

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 gives an implied usage context and a concrete search example ("Huawei SUN2000-10KTL"), which helps an agent call it correctly. However, it does not state when to use this tool versus siblings like suggest_inverter_c10_26, nor does it give explicit exclusions or prerequisites.

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