get_payroll_results

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

With no annotations, the description must fully disclose behavior. It only states the tool retrieves data, but omits details like authentication needs, rate limits, pagination, or whether results are real-time or cached. The read-only intent is implied but not explicit.

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?

The description is structured as a docstring with parameter explanations, placing the core purpose first. It is relatively concise (about 4 lines of actual content), though the colon and indentation add minor verbosity.

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?

Despite no output schema or annotations, the description does not specify the return structure beyond 'earnings and deductions', nor does it mention error handling, permissions, or data scoping. This is insufficient for a payroll results tool.

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?

The description adds crucial meaning beyond the schema's basic type/title. It explains employee_id as EMPLID, clarifies that calendar_run defaults to the latest run, and documents element_type values ('earnings', 'deductions', 'all'). This fully compensates for the schema's 0% coverage.

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 uses a specific verb-resource combination ('Get earnings and deductions results for an employee's payroll run'), clearly distinguishing the tool from siblings like get_payroll_status or get_payment_info.

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 guidance is given on when to use this tool versus alternatives (e.g., get_payroll_status, list_calendar_runs). There is no mention of prerequisites, exclusions, or typical use cases.

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