journal_ventes

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

With no annotations, the description carries the full burden. It does disclose two useful traits beyond the name: the accounting permission requirement and the one-entry-per-invoice-and-credit-note output granularity. However, it says nothing about pagination, ordering, volume limits, or return format for a period report.

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 packs purpose, date format, entry granularity, and the permission prerequisite with no redundant filler. Efficient, though the parenthetical date format interrupts the purpose statement slightly.

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 two-parameter read report with no output schema and no annotations, the description covers the essentials: what it returns, the required date format, and the auth requirement. Output structure is only summarized, but that is adequate at this 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?

Schema description coverage is 0%, so the description must compensate. It supplies the critical missing semantic — the date format (AAAA-MM-JJ) — and clarifies that the two parameters bound a period, which the schema alone (bare 'Debut'/'Fin' titles) does not convey.

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 (journal des ventes) with scope (sur une période) and defines the granularity: one entry per invoice and credit note. An agent can infer it differs from journal_achats, but the sibling is never named explicitly, so differentiation is left to inference.

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?

There is no explicit when-to-use guidance or statement of when a different tool (e.g. journal_achats, export_fec, recap_tva) would be preferred. The accounting-permission prerequisite is mentioned, but that is a precondition rather than selection guidance.

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