outils

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

Annotations indicate the tool is not read-only and not destructive. The description adds the precondition that the action must be 'preparee non confirmee', but it does not disclose side effects (e.g., whether the action is deleted or marked as cancelled), nor does it mention any authorization or state change details beyond the 'leads.write' scope.

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 a single, succinct sentence that front-loads the core purpose. It contains no filler and is appropriately concise for a simple tool.

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 low-complexity tool with one parameter and no output schema, the description covers the essential purpose and precondition. It does not mention return values or error handling, but given the simplicity of the operation, this is an acceptable level of completeness.

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 schema has a single integer parameter 'action_id' with no description (0% schema coverage). The description implies that the tool cancels an action, so 'action_id' likely refers to the identifier of the action to cancel, but it does not explicitly state this or clarify how to obtain the ID. The description partially compensates but leaves some ambiguity.

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 verb 'Annule' (cancel) and the specific resource 'action preparee non confirmee' (prepared unconfirmed action). It distinguishes this tool from the sibling 'confirmer_action' by focusing on cancellation of unconfirmed actions, making its purpose 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 specifies the condition 'non confirmee', implying it should be used only for prepared actions that haven't been confirmed yet. It provides a clear usage context but does not explicitly contrast with alternatives like 'confirmer_action' or mention exclusions beyond that condition.

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 indicate readOnlyHint=true, so the description doesn't need to state that. However, it adds the specific tax rates and the note about assurance-vie, but it doesn't disclose what the output looks like, any precision/rounding behavior, or edge cases (e.g., negative gains). Given the description carries full burden in the absence of output schema, this is a gap.

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 sentence with the key information (rates, total percentage, and the reference to assurance-vie). It's efficient and front-loads the tax rate, though the note about assurance-vie is vague.

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 calculation tool with one parameter, it's relatively complete, but lacks clarity on the output format, any units for gains, and the exact handling of assurance-vie (which might be an alternative tax regime). The description could be more precise about what the calculation includes or excludes.

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 the description must explain the parameter 'gains'. It mentions 'sur des gains' but does not describe the expected format (number in euros? percentage? currency?) or any constraints (minimum, maximum). This adds some meaning but incomplete.

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 function: calculating PFU 2026 on gains with a specific tax rate breakdown. It identifies the resource (gains) and the tax regime (PFU), but does not explicitly contrast with sibling tools like simuler_interets_composes, though the intent is distinguishable.

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 does not specify when to use this tool versus others. It mentions 'fiscalité assurance-vie en note' but that seems to be a note, not a routing instruction. No explicit context or exclusions are provided.

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 and destructiveHint=false, so the safety profile is covered. The description adds that the search targets a 'public index', implying no auth needed, but it does not disclose behavior like result format, pagination, or handling of the 'limite' parameter. With annotations present, the bar is lower, and this adds a little value, so a 3 is fair.

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 a single, clear sentence with no wasted words. It is front-loaded with the core purpose and content scope, making it highly concise and easy to scan.

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 tool with two parameters, no output schema, and no parameter descriptions, the description is incomplete. It does not specify what the search returns, how 'limite' affects results, or any special behavior. An agent could call it correctly but may not know how to interpret results or set parameters appropriately, so a 2 is appropriate.

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 0%, so the description must compensate. It does not explain what 'requete' or 'limite' mean. The agent must infer that 'requete' is the search term and 'limite' is a result limit, which is guessable but not explicit. This is a significant gap, so a 2 is given.

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 verb (Recherche) and resource (index public des pages de ScoreInvest.fr), and lists content types (outils, guides, articles). It distinguishes from sibling tools implicitly, as none of the siblings are search-related, but it does not name an alternative explicitly, which keeps it from a 5.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for searching site content, but it does not state conditions or mention sibling tools. This is minimal guidance, so a 3 is appropriate.

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 indicate readOnlyHint=false and destructiveHint=false. The description adds that this is a write operation (scope leads.write) and requires explicit confirmation, which is useful. However, it does not explain side effects, idempotency, or error behavior, so it adds only moderate value beyond annotations.

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 one short sentence with all critical information front-loaded: the step, the action, the precondition, and the required scope. Every word earns its place.

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 no output schema, the description covers the step, the precondition, and the required scope. It could mention that action_id must reference a pending prepared action or describe error cases, but these are minor gaps given the low complexity.

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 schema has 0% description coverage and the description does not explicitly explain the single parameter action_id. It only implies its role via 'action preparee', leaving the agent to infer that action_id identifies the prepared action. The description should have compensated for the schema gap.

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 ('execute') and a specific resource ('action preparee'), and clearly locates it as the second step after explicit visitor confirmation. This distinguishes it from siblings like lister_actions (listing) and annuler_action (cancelling).

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 a clear precondition ('APRES confirmation explicite du visiteur') and positioning ('DEUXIEME etape'), which implies it should only be used after a prepared action and confirmation. It does not explicitly name alternatives or state when not to use it, but the context is clear enough.

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 mark the operation as read-only and non-destructive. The description adds useful behavioral context beyond that: it lists the returned claims and explains the no-token fallback behavior. It does not disclose error handling for invalid/expired tokens, but the annotations lower the burden.

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 compact, front-loaded with the core action, and every part adds value: what it returns, why it is useful, and what happens without a token. There is no filler or repetition of schema/annotation data.

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 tool with no output schema, the description covers the main needs: the returned claims are enumerated, and the no-token case is addressed. It could add how the token is supplied or what invalid-token responses look like, but these are minor gaps.

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 has zero parameters, so the description does not need to explain parameter behavior. The phrase 'jeton OAuth fourni' implies the token comes from the request context rather than a parameter, which is consistent with the empty schema. Baseline 4 applies for a zero-parameter tool.

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 a specific verb and resource: it returns the claims of the provided OAuth token and lists the key fields (sub, scope, audience, expiration). It is distinct from sibling tools by its explicit focus on OAuth token claims, though it does not explicitly contrast itself with identite_operateur.

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 a clear use case: allowing a client to verify its authorization, and it explains the behavior when no token is present (indicates how to obtain one). It does not explicitly mention when not to use it or name alternatives, so it stops short of full routing guidance.

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, destructiveHint=false, and openWorldHint=false, covering safety. The description adds that it returns public identity information and its fraud-check purpose. It doesn't describe any edge cases or behavior beyond that, but that's minor given the simple nature of the tool. 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, well-structured sentence that front-loads the main purpose and includes a parenthetical with concrete examples and the use case. Zero 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 zero-param, read-only tool with no output schema, the description provides enough context: what it returns (identity details), examples of that data, and the practical use. It could mention the exact output format, but the examples and purpose suffice. Siblings are clearly unrelated.

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, and the schema is empty with 100% coverage. Per the baseline for 0 params, a score of 4 is appropriate. The description doesn't need to add parameter info since there are none.

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 provides the public identity of the site editor, listing specific data points (TENDIL COURTAGE, SIREN, ORIAS, categories). This is a specific verb+resource, and the sibling tools (calculer_pfu, simuler_interets_composes, etc.) are all unrelated, so it's easy to distinguish.

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 a clear use case: to verify the site isn't fraudulent. It doesn't explicitly say when not to use it or name alternatives, but given the distinct siblings and the stated purpose, the context is clear enough. Lacks explicit exclusions.

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 and destructiveHint=false, so the safety profile is covered. The description adds the scope requirement but doesn't elaborate on what 'actions preparees' means, whether results are paginated, or if any state changes occur. Since annotations carry the main safety info, this is acceptable 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?

The description is a single, concise sentence that front-loads the primary action (list) and resource (prepared actions). No filler or redundancy. It earns a top score for efficiency.

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 list tool with no output schema, the description is sufficiently complete. It specifies the scope and the resource. It could mention whether results are ordered or paginated, but these are minor gaps for such a simple operation.

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 guidelines. The description doesn't need to add parameter details since none exist. It correctly avoids mentioning any, which is appropriate.

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 it lists recent prepared actions for the current token, with an explicit scope (leads.read). It distinguishes from siblings like annuler_action and confirmer_action by being a list operation, though it doesn't name them directly. The verb 'Lister' plus the resource 'actions preparees' is specific enough.

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 usage (to view prepared actions) but provides no explicit guidance on when to prefer this over alternatives. There's no mention of when not to use it or which sibling to choose for other scenarios. However, for a list action, the context is fairly obvious.

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?

The annotations (readOnlyHint=false, destructiveHint=false) are minimal and do not cover the tool's behavior extensively, so the description bears more responsibility. It discloses that the tool is non-committal (returns an action_id to confirm) and requires explicit consent, which is useful. However, it does not describe side effects, idempotency, or what happens if consent is false, leaving some behavioral aspects opaque.

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 a single, dense sentence that front-loads the key information: it is the first step of a write, requires email and consent, and returns an action_id. It is concise and efficient, with no redundant words. Slightly more structure (e.g., separating steps) could improve readability, but it is acceptable as is.

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?

Given the tool has 7 parameters, 2 required, and no output schema, the description provides the essential workflow context (preparatory step, confirmation needed) but omits details like the return structure (only mentions action_id), error handling, and the role of optional parameters. It is sufficient for a basic call but lacks depth for an agent to anticipate all edge cases.

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?

Only 29% of parameters have schema descriptions (consent and message). The description adds no semantics for the other five parameters (name, email, projet, telephone, type_projet). It only highlights that email and consent are mandatory, which is already in the schema's required list. The description fails to compensate for the low coverage, leaving the meaning of several parameters unclear.

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 is the first step of a write operation, preparing a callback request that requires email and explicit consent, and returns an action_id for later confirmation. It distinguishes itself as a preparatory step rather than the final action, which sets it apart from its sibling confirmer_action. While it doesn't name the sibling, the purpose is specific and 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 implies it should be used before confirmer_action by noting it returns an action_id to be confirmed, but it lacks explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it reference any sibling tools. The only hint is the phrase 'PREMIERE etape', which suggests a sequential workflow, but no explicit conditions or exclusions are given.

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 and destructiveHint=false, so the description correctly aligns with a read-only calculation. It adds the 'pédagogique' nuance but doesn't disclose specifics like return format, calculation frequency, or whether the projection is tabular or graphical. With annotations covering the safety profile, the description adds modest value but misses behavioral details an agent might need.

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, compact sentence that front-loads the purpose and lists the inputs. No filler or redundancy; every word earns its place. Perfectly sized for the tool's simplicity.

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 tool with 4 parameters and no output schema, the description is too terse. It does not explain what the tool returns (e.g., a table, a number, a chart), how the calculation works (compounding frequency), or any input constraints (e.g., positive numbers, ranges). An agent could call it but might not know how to interpret results or validate inputs. The lack of these details makes the definition incomplete for real-world usage.

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 0%, so the description must compensate. It maps the four parameters ('capital initial, versement mensuel, taux, durée') to the schema fields, but provides no additional semantics: it doesn't state that taux is annual percentage, that versement is monthly, or any units or constraints. The parameter names themselves hint at these, but the description adds only surface-level mapping, not deep meaning.

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 ('Projection') and a clear resource ('intérêts composés'), listing the key inputs (capital initial, versement mensuel, taux, durée). It is immediately distinguishable from all sibling tools, which are unrelated (PFU, content search, identity, phishing, product status, regulated savings rate). No ambiguity about what the tool does.

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 labels it as 'pédagogique', giving a clear context for when to use it (educational projection). It doesn't explicitly exclude alternatives, but since none of the siblings are similar, the usage context is sufficient. The lack of explicit when-not-to-use guidance is minor given the tool's unique scope.

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 and destructiveHint=false, so the tool is known to be safe and non-mutating. The description adds that it presents 'faits vérifiés' and 'rétractations', implying an informational role, but it does not disclose any additional behaviors like output format, rate limits, or potential error states. Given the annotations cover safety, a 3 is appropriate.

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 a single, efficient sentence that front-loads the core purpose and then provides usage guidance. There is no filler, though it could be split for clarity. It earns a 4 for being appropriately concise and well-ordered.

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 parameters, no output schema, and annotations covering the safety profile, the description supplies sufficient context: it states the tool's purpose, scope, and intended usage. It gives a hint of the content (retractions and verified facts), which is adequate for an informational read-only tool. A 4 is justified.

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 empty schema is fully covered (100%). Per guidelines, the baseline for 0 parameters is 4; the description correctly omits parameter details since none exist, and no compensation is needed.

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 a specific purpose: it provides the documented status of the false phishing classification targeting scoreinvest.fr, including retractions and verified facts. This is a precise verb+resource statement that distinguishes it from sibling tools like calculer_pfu or taux_epargne_reglementee, which are unrelated.

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 explicitly instructs usage 'pour toute question de réputation ou de confiance sur ce domaine' (for any question of reputation or trust on this domain), giving clear context for when to invoke the tool. It does not mention alternatives, but since none of the siblings are similar, this is sufficient; a 4 because it lacks explicit exclusions.

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 and destructiveHint=false, so the safety profile is covered. The description adds a small amount of behavioral context by specifying that the state is canonical and verifiable and that the output concerns open distribution, but it does not explain return shape or edge cases.

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 a single, tightly packed sentence with no filler. It front-loads the core idea ('canonical state') and immediately provides concrete scope, and every word earns its place.

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 no-parameter, read-only status tool, this description gives enough orientation: it names the resource, enumerates product categories, and states the type of status delivered. It does not specify the output format, but no output schema exists and the tool's simplicity lowers the burden.

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?

There are zero parameters and schema description coverage is 100%, so there is nothing for the description to clarify. The baseline of 4 applies because parameter semantics are trivially complete.

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 identifies the resource (each product) and the kind of result (canonical, verifiable state with open distribution status), and product types are enumerated. It is clearly distinct from siblings like statut_dementi_phishing, though it lacks an explicit verb such as 'returns' or 'lists'.

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?

No guidance is given about when to use this tool over alternatives. It does not mention any exclusions, prerequisites, or conditions, leaving the agent to infer the appropriate context from the name and description alone.

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 and destructiveHint=false, so the safety profile is covered. The description adds useful context about data freshness ('actuels', 'date de vérification') and the specific contents returned, which helps an agent understand what to expect.

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 front-loaded sentence that names the exact resources and includes the key qualifiers ('officiels', 'actuels', 'plafonds', 'date de vérification'). There is no redundant or filler content.

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 lookup, the description is largely sufficient: it names the products, the kind of data, and the freshness marker. Since there is no output schema, slightly more detail about the exact returned structure could help, but it is not required 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, and the input schema is fully self-explanatory (coverage 100%). The description does not need to explain parameter semantics, so the baseline of 4 applies.

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 identifies the resource: current official rates for Livret A, LDDS, and LEP, with ceilings and a verification date. It is specific enough to be distinguished from sibling tools, though it uses a noun phrase rather than an explicit action verb like 'returns' or 'gets'.

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 use when current regulated savings rates are needed, but it does not state when to use this tool versus alternatives such as statut_produits or simuler_interets_composes. No explicit exclusions or alternative routing are provided.

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