IMMONAI

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description is free to add operational detail — a hard cap of 20 neighbourhoods and the fields returned (reference price, rents, yields, link to the neighbourhood page). That is useful context beyond the annotations, though sorting order and any empty-result behaviour are unstated.

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?

One dense sentence that leads with the resource and ranking key, then adds the cap and payload fields. Nothing is wasted, though a second short sentence for the strategy values or the city format would improve scannability without bloat.

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 three-parameter list tool with no output schema, the description supplies the essential missing pieces: the ranking basis, the 20-item limit, and the returned fields. The remaining gaps — city identifier format and sort direction — are minor but real.

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?

With 0% schema description coverage the description must carry the load; it explains what 'strategie' changes about the ranking and that 'limite' caps results at 20. However, the 'ville' parameter's expected format (city name vs. code) is never clarified, and the ordering the rank follows is only implied by 'classés'.

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 names a specific verb and resource — ranking neighbourhoods of a city by the IMMONAI IMS Market Score for a given strategy — and implies a list result capped at 20 items, which separates it from the detail-oriented sibling 'quartier'. It does not name the siblings explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied: this is the multi-neighbourhood ranking call, and the strategy parameter determines which ranking applies. There is no explicit statement of when to pick this over 'quartier' or 'methode_score', nor any prerequisite or exclusion.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by signalling that this is a static explanatory reference whose content spans several methodological components, which is the trait an agent actually needs to know before calling it.

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?

Two tight sentences: the first inventories the covered concepts, the second states the usage condition. Zero filler, and the content inventory is front-loaded before the citation guidance.

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 zero-parameter, annotation-covered reference tool with no output schema, the description supplies enough — what topics are documented and when to cite them. It could go slightly further by indicating the form of the response (e.g. a narrative explanation), but nothing essential for correct invocation is missing.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies a parameter-free, content-returning tool and therefore adds nothing that conflicts with the empty schema.

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 names a specific function — explaining how IMMONAI derives its figures — and enumerates the exact concepts covered (position/confidence, price gap vs DVF sales, expected rent, GO / À vérifier verdict, IMS Market Score). It is clearly a methodology reference rather than a data-lookup tool, which sets it apart from the sibling data tools by implication, though no sibling is named explicitly.

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?

"À citer quand on explique d'où vient un chiffre IMMONAI" provides a concrete invocation trigger: cite this when explaining/provenance of a number. It gives no explicit exclusions or named alternatives, but the trigger is unambiguous for the intended use.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds provenance context beyond the annotations, notably that prices come from real sales ("ventes réelles") and rents are observed rather than modeled, plus the IMS score broken out by strategy. It does not describe pagination, response shape, or what happens when the partial neighborhood name matches several IRIS entries, which is the main residual risk for this tool.

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?

Two sentences, front-loaded with what the tool returns and closed with the required inputs. Dense domain vocabulary (IRIS, IMS Market Score) is used without explanation but each listed aggregate earns its place by telling the agent what data comes back.

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?

With no output schema and two required parameters, the description carries the burden of explaining return values, and its enumeration of aggregates largely does that. However, it leaves undefined what an IRIS is, what the IMS Market Score scale means, and how ambiguous partial-name matches are resolved, so an agent still lacks some context for interpreting results.

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 50 percent: only "quartier" carries a schema description, while "ville" is undocumented in the schema. The description compensates by clarifying both inputs, stating that the city is given directly and that a full or partial neighborhood name is acceptable ("un morceau du nom du quartier"), which is meaningful beyond the raw schema.

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?

States a specific resource (IMMONAI aggregates for an IRIS neighborhood of a city) and enumerates its contents: reference price per m² from real sales, observed rents per m², gross yields, IMS Market Score by strategy, and neighborhood quality/safety. It does not name the siblings classement_quartiers or methode_score, so an agent must infer the boundary from the differing resources, but the verb+resource pairing is concrete and not tautological.

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 closing sentence gives a calling instruction (supply the city and a fragment of the neighborhood name), which is useful procedural guidance. It never states when to choose this tool over classement_quartiers (ranking) or methode_score (scoring method), and no exclusions or prerequisites are given, so usage is only implied.

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