get_salary

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

No annotations are provided, so the description must fully disclose behavior. It only states that it gets details, without mentioning error behavior, required permissions, or response structure. The word 'details' adds minimal context beyond the tool name.

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 in French, with no redundant words. It is efficiently front-loaded and every word contributes to the purpose.

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?

The tool is simple with one parameter, but the description is very thin: no output schema, no annotations, and no clarification of what 'details' contains. It also lacks guidance on how to obtain the id (e.g., via list_salaries). Given the low complexity, a slightly richer description is expected.

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 one parameter 'id' with no description (0% coverage), and the description does not mention the parameter at all. It fails to clarify what 'id' refers to, leaving the agent to infer it is the salary id without any confirmation.

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 'Obtenir' (get) and the resource 'fiche de salaire' (payslip), indicating a retrieval operation for a specific salary record. This distinguishes it from sibling tools like list_salaries and create_salary.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it fetches a single record by id, nor does it suggest pairing with list_salaries to obtain the id. There is no contextual instruction.

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