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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds value beyond them by disclosing the admin-rights requirement for the "people" detail level. It does not mention pagination or default date-range behavior, which is the remaining gap.

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?

Two tight sentences with no filler, and the return-content list is front-loaded before the detail-level caveat. The telegraphic style is dense but readable and every clause carries 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?

With no output schema, the description usefully enumerates what the call returns and the one access constraint, which is enough for an agent to call it confidently. Minor omission: no statement of default date window or what an omitted date range returns.

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 low at 25% (only "company" is documented in the schema), so the description carries extra burden; it clarifies the "people" enum value meaning and its permission requirement, which the schema does not. However, it says nothing about from/to semantics or defaults, leaving half the parameters dependent on bare patterns.

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 and enumerates the returned metrics (gross, employer taxes, net, total cost, next run estimate, headcount, contractors), which lets an agent distinguish it from sibling aggregates like get_metric or get_reports. It stops short of naming a sibling it is not, but the payroll-specific scope is unambiguous.

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 an explicit conditional: per-person pay is only returned with detail "people", and that mode requires payroll admin rights, which is a real prerequisite an agent must check. It does not contrast with an alternative tool, but the mode selection guidance is concrete and actionable.

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