QUAND guides_liste a rendu un slug pertinent et qu'il faut le contenu complet de la procédure. Lit un guide officiel Synergieloc en Markdown complet (slug obtenu via guides_liste). GRATUIT, aucune unité, aucune clé requise.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ex. quittance-loyer, revision-loyer-irl |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool is free and requires no units or keys, implying it is a safe read operation. However, it does not explicitly confirm non-destructiveness or detail response format beyond 'Markdown complet'. Adequate but not exhaustive.
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 concise sentences, front-loaded with the usage condition and action. Every sentence adds value without 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 simple read tool with one parameter and no output schema, the description sufficiently explains purpose, prerequisites, and output type. It could mention the nature of the Markdown content (e.g., length or structure), but remains adequate.
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 100% with a single parameter and example values. The description adds value by explaining that the slug comes from guides_liste, providing context beyond the 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 clearly states the tool reads a full Synergieloc guide in Markdown given a slug, and distinguishes it from the sibling guides_liste by specifying it is used after that tool returns a slug.
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?
Explicitly states when to use: 'WHEN guides_liste has returned a relevant slug and you need the full content.' This provides clear context and differentiates from the sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct by purpose (e.g., quittance_loyer vs relance_impaye, or relance_facture_client vs relance_impaye). A few pairs like bon_intervention and fiche_mission could cause confusion, but detailed descriptions help resolve ambiguity.
Tool names mix French and English, and use inconsistent patterns: some are noun-based (annonce_location, quittance_loyer), some verb-based (decide_campagne, obtenir_cle_api), and the cao_* tools use a prefix convention. Still readable but not uniform.
41 tools is excessive for most servers, even one covering real estate and CAD. While the breadth is justified by multiple subdomains, the sheer number makes the surface hard to navigate and suggests possible over-fragmentation.
The tool set covers a wide range: rental lifecycle (annonce, EDL, quittance, relance), owner reporting, artisan documents, fiscal synthesis, CAD generation and verification, outreach, and guides. Minor gaps exist (e.g., no direct tenant/property CRUD), but for a document-generation server it is quite complete.
