hr.run_payroll_report

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

With no annotations present, the description must fully disclose behavioral traits. It states 'Generate' but does not clarify if this is a read-only operation, if it triggers background processing, or if it has side effects. No mention of required permissions or data mutability. The term 'Shows' implies read access, but the mutation potential is unclear.

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 efficient sentences clearly convey the purpose and content without any unnecessary words. Front-loading the main action ('Generate a payroll report') followed by supporting details makes it easy to parse.

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?

The tool has no output schema, so the description should partially fill that gap. It mentions what is shown but omits format, pagination, and any security or authorization requirements. Given the sensitivity of payroll data, permission context is missing. Complexity is moderate but not fully addressed.

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 input schema has 100% description coverage for both parameters (period and department). The description adds value by explaining that the report includes compensation, tax withholdings, and bank account details, which goes beyond the schema's minimal descriptions.

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 clearly states 'Generate a payroll report' (verb+resource) and specifies the report contents (compensation, tax withholdings, bank account details). It distinguishes from sibling tools like fin.export_financial_data and other HR tools such as hr.search_employees, which have different purposes.

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 provided on when to use this tool versus alternatives, such as when to use fin.export_financial_data for broader financial reports or hr.search_employees for individual employee details. There are no explicit use-case descriptions or exclusions.

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