create_salary_record

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

With no annotations, the description carries the full burden and does disclose the key trait: the call writes a real payroll record affecting accounting and HR data, and `data` is sent verbatim. It leaves out auth/permission requirements, error behavior on invalid payloads, and what the response returns, keeping it short of a 5.

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?

Three short clauses, front-loaded with the WRITE marker and the highest-stakes fact (real payroll/accounting impact), followed by the prerequisite and the payload pointer. Nothing is redundant.

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 mutation tool with a free-form nested body, no annotations and no output schema, the description covers impact, prerequisite, and where to find the payload spec. Missing only response/return behavior and permission scope to be fully 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?

Schema coverage is 100%, so baseline is 3, and the description adds real value by explaining the single param is passed verbatim as the request body and by pointing to the external API reference and defaults tool for the nested object's expected shape — something the flat schema cannot express.

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 states a specific verb and resource ('creates a real payroll record in Holded') plus the API version, and the 'WRITE' prefix makes the mutating nature unmistakable against read siblings like get_salary_record or list_salary_records.

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?

It explicitly names a prerequisite path — 'Use get_salary_record_defaults first to obtain a valid base payload' — which routes the agent to the right sibling before calling. It doesn't spell out the create-vs-update decision, but the verb plus the defaults prerequisite gives clear context.

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