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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds the domain meaning of records (status and dates attached to people), but says nothing about pagination behavior, result volume, or permissions despite the schema hinting at a next_page pattern.

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 short clauses, front-loaded with what the resource is, then filters, then endpoint. No filler sentences and nothing redundant.

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 five-parameter list tool with no output schema, the description covers purpose and filter intent but leaves out pagination guidance and what a qualification record contains beyond 'status and dates'. Adequate, not complete.

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 60%: page and limit are well documented, but employee_number and qualification_library_item_id have no schema descriptions. The description's 'filter by person, employee number or library item' does give semantic meaning to those two undocumented filters, but adds no format, multiplicity (single vs comma-separated) or matching-behavior detail.

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 resource (qualification records: licences, certificates) with the data it carries (status, dates) and the endpoint. The parenthetical examples implicitly separate it from siblings like intellihr_list_person_skills and intellihr_list_trainings, though it never names those alternatives explicitly.

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?

'Filter by person, employee number or library item' gives implied usage context, but there is no when-to-use/when-not-to-use framing and no pointer to a sibling for related data (e.g. person skills vs qualifications).

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