My Absences (Personio)

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

The description adds 'Your' to indicate it returns the user's own absences, which is not in annotations. Annotations already declare readOnlyHint, idempotentHint, etc., so the description complements them well without contradiction.

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?

The description is two sentences, front-loaded with the core purpose, and every word adds value. No redundancy.

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?

Despite having 5 optional parameters and no output schema, the description omits pagination (cursor, limit), date filtering (endsBefore, startsAfter), and any mention of return format. It is too brief for a listing tool with such configuration.

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?

Of the 5 parameters, only includeBalance is explained (toggle for returning balance). The other 4 (limit, cursor, endsBefore, startsAfter) have no description, and schema coverage is 0%. This leaves pagination and date filtering undocumented.

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?

The description clearly states it returns 'absence periods' for the user, which matches the tool name. While it doesn't explicitly differentiate from siblings like personio_request_absence, the verb 'get' and resource 'absences' are clear enough. The mention of includeBalance adds specificity.

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?

The description provides a usage hint for includeBalance parameter but does not guide when to use this tool over siblings. For example, it doesn't mention that this is for the user's own absences only, or contrast with personio_request_absence.

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