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

Annotations already establish readOnly/openWorld/non-destructive, so the description's main value-add is the 'Sensitive payroll data' warning and the per-type preconditions that determine whether a call is valid at all. It does not mention pagination behavior or the fact that results may be paged via next_page, though the schema params hint at it.

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?

Dense and front-loaded: the resource, the conditional parameter rules, the optional filters, and the data sensitivity warning are all delivered in a few short clauses with zero repetition of schema text. Nothing could be removed without losing routing or validity information.

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 9-param, single-required-param list tool with no output schema, the description covers the difficult part (type-dependent required parameters) and names related lookup tools. Missing only a note on pagination/next_page continuation and possible edge cases where types conflict.

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%, so the parameter-level text is already documented; the description nonetheless adds genuine meaning by binding parameters to the type enum (which pair is required under which type), which the schema cannot express. Value is added beyond baseline without being complete on cross-parameter interactions.

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 and resource ("Payroll transactions per employee for one settlement type") and immediately scopes it by the settlement type enum values. It is clearly distinguishable from siblings like jisr_list_gl_transaction_types or jisr_get_employee_monthly_payables, which it does not overlap with.

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 conditional guidance: 'payrun' needs pay_period and paygroup_id, while the other three types need a from/to range, and it points to jisr_list_gl_transaction_types for transaction type ids. It stops short of saying when to prefer a sibling tool (e.g., financial info vs payroll transactions) or what to do when both date and period could apply.

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