calculate_dpe_energy_class

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

No annotations are provided, so the description must carry the full burden. It only states 'Returns: {note}', a placeholder, without detailing output format, side effects, or authentication needs. The behavioral disclosure is insufficient.

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 extremely concise: two sentences. The first sentence directly states the purpose, and the second provides a return placeholder and a useful pointer to related tools. No wasted words.

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 simple one-parameter tool with an output schema, the description provides the basic purpose. However, the return value is vaguely indicated by '{note}', which is uninformative. The description could more explicitly state that the output is the energy class letter.

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 fully describes the parameter 'kwh_m2_year' with a clear description. The description merely repeats 'primary energy consumption', adding no new semantic value. With 100% schema coverage, the baseline is 3.

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 the tool's purpose: determining the French DPE energy class from primary energy consumption. It distinguishes itself from siblings by referencing the DPE context and directing users to 'list_bundles' for related calculators.

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 implies the tool should be used when a user needs to compute a DPE energy class given energy consumption. It lacks explicit guidance on when not to use it or alternatives, though it suggests viewing 'list_bundles' for related tools.

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