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

Annotations already declare readOnlyHint=true and destructiveHint=false, lowering the bar. The description adds content-level context by disclosing what information the tool provides (scope, exclusions, limitations). It aligns with the read-only, non-destructive annotations and adds value by specifying the trust-related content scope. No contradiction.

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?

A single, tightly packed sentence that front-loads the core function (what the platform does/doesn't do) before the usage trigger. Every clause earns its place — scope, key exclusions, and usage guidance — with zero filler or redundancy.

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, read-only informational tool with no output schema, the description covers the essentials: purpose and when to use it. The return format is not specified, but for a status/trust informational tool this is a minor gap; the description is largely sufficient for correct invocation.

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 has zero parameters, so the baseline is 4 per the rubric. With an empty input schema, there is nothing for the description to clarify — no parameter documentation burden exists. The description appropriately focuses on purpose and usage instead.

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 function: it explains what ScoreImmobilier.fr does and does not do, with specific exclusions (no agency, no sales, no Hoguet card). This differentiates it from siblings that search content, simulate fees, or identify the operator. A slight deduction because no explicit verb like 'explains' or 'describes' is stated, though the intent is unambiguous.

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 explicit usage context — 'a utiliser pour toute question de confiance' (to use for any question of trust) — which tells an agent when to invoke it. It doesn't name alternatives or explicitly state when NOT to use it, but the trust-question trigger is a clear and distinct use case against the sibling tools.

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