import_leave_periods

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false. The description adds two pieces of context the annotations cannot: that file_path resolves on the server's filesystem (an important security/location constraint) and that the report names every refused line, disclosing partial-failure semantics. Idempotency/duplicate handling remains unaddressed.

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 sentences, front-loaded with the core action before the input-mode details. The closing sentence about refused lines is slightly awkwardly phrased but earns its place by conveying failure behavior.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values. It covers sources, server-side path semantics, and partial-failure reporting, leaving only cross-sibling routing and permission prerequisites uncovered.

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% and the format is self-documenting via the ImportFormat enum, so the schema carries the burden. The description reinforces the inline-vs-path distinction but adds no syntax, format, or mutual-exclusivity rules beyond what the schema already states.

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 (import leave periods) and the accepted source formats (CSV/XLSX). It does not explicitly distinguish itself from siblings like create_leave_period or list_leave_periods, but an agent can infer the bulk-import scope from the name and text.

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?

It explains the two input modes (inline content vs. a path on the server machine) which is genuinely useful routing guidance. However, it never says when to use this bulk importer instead of the single-record create_leave_period sibling, nor prerequisites such as required permissions.

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