get_payment_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it gets payment details, without revealing whether it is read-only, any side effects, error conditions, or response structure. The return value is only vaguely described as 'including net pay and payment method'.

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 concise, consisting of a single sentence plus parameter documentation. It includes the return value hint, achieving maximum information density with minimal words. No superfluous content.

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 is simple with 2 parameters and no output schema. The description provides essential information but lacks details on error handling, data volume, or potential constraints. It is minimally adequate for a straightforward retrieval 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 significant meaning beyond the input schema. It explains the employee_id as 'EMPLID' and the optional calendar_run with behavior ('If not provided, returns latest'). Given 0% schema description coverage, the description fully compensates by clarifying each parameter's purpose and default behavior.

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 the tool gets payment preparation and payment details for an employee. The verb 'get' and resource 'payment details' are specific. Among siblings like get_payroll_results and get_payroll_status, this tool is distinctly focused on payment preparation and details including net pay and method.

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?

The description does not provide any guidance on when to use this tool versus alternatives like get_payroll_results or get_payroll_status. There is no mention of prerequisites, scenarios, or when not to use it.

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