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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds substantial domain behavior: the template is master data, it changes future payslips only, it posts nothing to the ledger, and updates replace the full line set. It still omits permissions and validation behavior, so not 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?

Four sentences, each earning its place: first defines the resource, second gives create/update routing, third gives update replacement semantics, fourth gives ledger/master-data behavior. It is front-loaded and waste-free.

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 6-parameter tool with 0% schema coverage and no output schema, the description covers core usage and important behavioral context well. It is incomplete on several secondary parameters (notes, archived, statutory) and most nested line fields, leaving the agent to infer their meaning from names alone.

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 0%, so the description must carry the burden. It explains id semantics (omit to create, pass to update) and the replacement behavior of lines, and names several line fields (kind, rate, quantity, amount, formula). However, top-level notes, archived, and statutory are never mentioned, and many line fields (code, role, sort, payitem, prorate, category, description) remain undocumented.

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?

States a specific verb+resource ('Create or update a payslip template') and defines what the resource is ('a named line set of earnings, deductions and contributions'). This clearly distinguishes it from sibling tools like save_payslip and list_payslip_templates.

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?

Gives explicit create-vs-update routing ('Omit id to create; pass an id to update that template') and a key update constraint ('On update, lines is the full set'). It does not name alternative tools or when-not-to-use this one, so it falls short of a full 5.

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