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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered externally. The description contributes the concrete REST endpoint and the entity's field set, but says nothing about rate limits, page-size defaults, or result shape beyond what annotations and schema supply.

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 compact clauses with zero filler; the field subset is front-loaded alongside the verb. Slightly truncated rather than verbose, but efficient.

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?

All parameters are optional and well described in the schema, and there is no output schema, so the parenthetical field list usefully signals return contents. However, with six parameters and a highly similar organization-positions sibling, the description leaves paging behavior and disambiguation 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 description coverage is 100%, so all six parameters (top, skip, count, filter, orderby, company_id) are already fully documented, including the filter syntax example and company_id fallback. The description adds no parameter-level meaning beyond the field list, so baseline 3 applies.

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 and resource ('List employee position records') and enumerates the salient fields (job, organization unit, grade, manager, effective dates), plus the underlying OData entity. It is clear apart from most siblings, though it never explains how it differs from the closely named payspace_list_organization_positions.

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 when-to-use, when-not-to-use, or alternative guidance is given. An agent must infer from the name alone that this is the record source for an employee's job/grade/manager assignment rather than, say, payspace_list_jobs or payspace_list_organization_units.

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