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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real behavioral context on top: pagination continuation via next_offset, the scope of `search` matching, and the filter expression format. It doesn't mention result counts or default ordering, but nothing contradicts the read-only annotation.

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 sentences, front-loaded with what the tool returns, then paging, then parameter hints. No repetition of schema text and no filler.

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 6-parameter, no-output-schema list tool, the description compensates well by enumerating returned fields and pointing to talenthr_get_directory_filters for valid filter keys. Minor gaps remain around sort/order and whether unpaged calls silently truncate at the default limit of 10.

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?

With 83% schema coverage the baseline is 3, and the description earns above it by explaining `search` semantics (name, description, category) and giving a concrete filter example (status=1,2;category=19) that shows multi-value syntax. Sort/order behavior is left entirely to the schema.

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?

Specific verb ('List') plus resource ('company's assets') plus the exact fields returned (status, category, serial number, cost, purchase/warranty dates). The qualifier 'company's' implicitly distinguishes it from the per-employee sibling talenthr_get_employee_assets, so an agent can route between the two without opening a schema.

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?

Gives concrete operational guidance: page with next_offset, use `search` to match name/description/category, use `filter` for status and category ids. It does not explicitly say when to prefer this over talenthr_get_employee_assets, so it stops short of full alternative routing, but the intended usage is clear.

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