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

readOnlyHint=true already establishes the safety profile, so the bar is lower, but the description does add real context: it flags sensitive content ('Contains pay data') and lists exactly which payroll components are returned. It says nothing about pagination behavior, permission requirements, or whether pay data is visible to the calling user, which would matter for a financial-data read.

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 tight fragments, front-loaded with the resource and scope, then the payload contents, then the endpoint. Nothing is wasted and nothing is buried.

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?

No output schema exists, so the description shoulders the burden of describing the return value — and it does, enumerating pay settings, attendance, leave, overtime, and totals at per-employee granularity. Combined with fully documented pagination params and a readOnly annotation, an agent has everything needed to call it correctly.

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% — limit, offset, and pay_period_id all carry clear descriptions, including the cross-reference to rotacloud_list_pay_periods for the id. The description adds no parameter semantics beyond what the schema already documents, so baseline 3 applies.

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 — retrieving payroll for one pay period, broken down per employee — and enumerates the visible content (pay settings, attendance, leave, overtime, totals). It is clearly distinguishable from rotacloud_list_pay_periods, though it never names a sibling or states the exclusion explicitly.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives such as rotacloud_list_pay_periods (the source of pay_period_id) or the leave/attendance tools that overlap with its content. The only routing hint lives in the schema parameter description, not the tool description.

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