dpe_logement

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

No annotations provided, so description carries full burden. It discloses output fields and source (ADEME) but lacks details on behavior such as error handling, rate limits, or authentication needs. For a read-only query tool, the description is adequate but not rich.

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?

Description is concise with four lines plus an Args section that reiterates parameters with examples. Every sentence adds value, though the Args section partially duplicates schema info. Overall well-structured and front-loaded.

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?

Tool has only two parameters and an output schema (present but not shown). Description explains key return fields. For its simplicity, coverage is good; lacks only minor details like error conditions or pagination.

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%, so description compensates by explaining both parameters: code_postal as 5-digit zip code with example, adresse as optional text to refine. Adds meaningful context beyond the schema's type and default values.

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?

Description clearly states it returns DPE diagnostics with specific output fields (energy label, GES label, surface, consumption, date) and filtering by postal code and optionally address. This verb+resource definition distinguishes it from sibling tools like geocode_address or risques_immobilier.

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?

Description implies usage context by mentioning filtering by postal code and address, but does not explicitly state when to use this tool versus alternatives, nor provides exclusions or prerequisites. Sibling tools differ in function but no comparative guidance given.

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