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

Adds meaningful behavior beyond the readOnlyHint annotation: sensitive fields (ID and tax numbers) are suppressed, and a non-matching id is treated as an error rather than an empty result. This clarifies privacy and failure semantics, though it doesn't cover pagination or exact error format.

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 sentences with no waste, and the core purpose is front-loaded ahead of the field/error caveats.

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?

For a single-record getter with no output schema, the description supplies the return shape (same fields as list_employees) plus privacy and error behavior. Only the exact error/response form is left implicit.

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 0% and there is one required id parameter, so the description carries the burden. It only restates 'by id' without giving format, type, or lookup expectations, adding marginal value over the bare schema property.

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 (get) and resource (payroll employee) scoped by id, and anchors the return shape by referencing the sibling list_employees. It is immediately clear what the tool returns, though the differentiation from list_employees is about field parity rather than use case.

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?

Usage is implied by 'one payroll employee by id' and the comparison to list_employees, but there is no explicit when-to-use guidance or named alternative (e.g., use list_employees to enumerate). The agent must infer the single-record vs list routing.

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