gerent365_get_attendance

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

No annotations are provided, so the description carries the full burden. It only states the tool gets attendance records and can filter; it does not disclose read-only nature, required permissions, output format, pagination, or other behavioral details. The verb implies retrieval but side effects are not explicitly ruled out.

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 a single concise sentence that immediately conveys the purpose and filtering capability. Every word contributes meaning with 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?

The tool is straightforward, but without annotations or an output schema, the description does not specify return values or edge cases. It covers the basic filtering options adequately, but leaves room for more detail on what the response looks like.

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 100% with each parameter described. The description restates that filtering by employee and date range is possible, but adds no new detail beyond the schema, such as parameter interactions or default values. Baseline 3 for high schema coverage is appropriate.

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 the tool retrieves attendance records (fichajes) using the verb 'Obtiene' (gets), and notes filtering by employee and date range. This distinguishes it from related siblings like get_last_punch (specific punch) and get_schedule (schedules).

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 implies usage for retrieving attendance records but doesn't explicitly state when to use this tool versus alternatives like get_last_punch. No exclusions or alternative recommendations are provided, so guidance is implied rather than explicit.

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