Détail d'une offre d'emploi

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds error behavior (404) and return format options, which goes beyond annotations. No contradictions; description complements structured hints.

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 purpose, no fluff. Efficiently conveys function, inputs, outputs, and error conditions. Every sentence adds value.

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 no output schema, description adequately lists returned fields. Covers error scenario. With annotations providing safety and idempotency, additional details (e.g., rate limits, pagination) are not critical. Completeness is adequate but not exhaustive.

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 100% (both parameters documented). Description adds real-world context (example '209WHZN') and explains purpose of the ID. Does not add new semantics for response_format beyond enum values. Baseline 3 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?

Description explicitly states it retrieves full details of a job offer by ID, lists returned fields (title, company, location, etc.), and distinguishes from sibling tool ft_search_offres which returns offer lists. Clear verb 'Récupère' + resource 'détail complet d'une offre'.

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?

Describes when to use: after obtaining ID from ft_search_offres. Implicitly suggests using ft_search_offres for listing and this tool for details. Mentions error 404 for invalid or expired IDs, providing context for error handling. No explicit alternatives or exclusions, but clear enough.

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