find_gaps

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

Adds useful context beyond readOnlyHint=true by disclosing the admin permission requirement. However, the pagination advice ('pass the last user uid from the previous page') conflicts with the schema, which exposes only 'page' and 'perPage' with no uid parameter — this mismatch is potentially misleading.

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?

Two tight sentences; the core operation is front-loaded and the pagination tip is secondary. No filler.

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 read-only tool with 5 params and no output schema, the description covers purpose, auth, and pagination but says nothing about the shape of results (a 'gap' record) and the pagination guidance diverges from the schema. Adequate but with clear gaps.

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%, so the schema documents several params (to, from, users) already. The description frames users as the subject and references date range and paging, but adds no syntax or clarification for page/perPage beyond what the schema provides, so it neither compensates for the gap nor adds much value.

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 (find) and domain resource (absences/gaps of given users) with scope (date range, admin). An agent can distinguish it from create_gaps and delete_gaps without opening schemas. The term 'absences' is domain jargon but contextualized well enough.

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 '(admin)' marker implies this requires elevated permissions, and pagination guidance is given, but there is no explicit when-to-use/when-not-to-use framing or comparison against alternatives like find_worklog_records. Usage is implied rather than stated.

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