My Attendances (Personio)

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

Annotations fully cover safety (read-only, idempotent, non-destructive). However, the description adds no behavioral context such as pagination support via cursor and limit, or date filtering via startsAfter/endsBefore. The agent is left guessing about output format or additional constraints.

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 extremely concise (5 words) but at the expense of completeness. It fails to convey enough information for the agent to use the tool correctly, so it is under-specified rather than efficiently concise.

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 no schema descriptions, no output schema, and a terse description, the tool is severely incomplete. Essential information about pagination, date filtering, and result format is missing, making it difficult for an agent to invoke correctly without additional knowledge.

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 0%, and the tool description provides no explanations for any of the 4 parameters (limit, cursor, endsBefore, startsAfter). The agent has no guidance on how to use filters or pagination.

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 'Your tracked work and break periods' indicates the resource but lacks an explicit verb like 'list' or 'get'. It distinguishes from sibling tools like absences and documents, but the wording is more like a label than an action description.

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 guidance on when to use this tool versus alternatives such as personio_record_attendance for entering attendances or personio_get_my_absences for absences. The description does not mention prerequisites or context.

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