get_thirdparty

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

With no annotations provided, the description carries the burden of disclosure. The verb 'Obtenir' suggests a read-only operation, but the description does not explicitly confirm no side effects, nor does it mention error handling, authentication, or response details beyond 'complete details.' This is minimal but not misleading.

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 is immediately understandable. Every word adds value, making it appropriately sized and well-structured.

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 getter, the description covers the basic purpose, but without an output schema it leaves the return structure undefined. A brief note on what 'complete details' includes or what 'third party' refers to in this context would make it more complete.

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 already provides 100% coverage for the single 'id' parameter. The description repeats that the ID is used but adds no new semantic details such as format, examples, or behavior for invalid IDs.

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 uses a specific verb ('Obtenir') and resource ('détails complets d'un tiers') and clarifies the lookup key (by its ID). It clearly distinguishes this from sibling tools like list_thirdparties or get_thirdparty_invoices by specifying the full-record retrieval via ID.

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 when a specific third-party ID is known and full details are needed, but it does not explicitly mention alternatives or exclusions. No when-not-to-use guidance is provided, so the implied context is minimal.

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