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

Beyond the readOnlyHint annotation, the description discloses real behavioral traits: the containment rule start>=from AND end<to, the hard 93-day window, and the exclusive upper boundary with the workaround of extending by a second. These are exactly the kind of gotchas that prevent wrong calls. It still says nothing about volume, pagination, or result shape.

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?

Only three sentences and the key constraint leads, but the prose is telegraphic: 'max93days here' and 'allow an extra second beyond the last desired end' read like notes to self rather than specification. No sentence is wasted, but several are compressed to the point of ambiguity.

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 output schema and 25% schema coverage across 4 parameters, the description should do more: it never says what an availability record contains, what the default `type` behavior is, or whether results are paginated. The interval semantics are well covered, so it is adequate rather than complete.

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 25% (only employeeID is documented), so the description carries most of the burden for `from`/`to` — and it does, defining the interval boundaries and the 93-day cap precisely. However the `type` enum (WORK/NO_WORK) is never mentioned in the description, leaving a filtering parameter unexplained in both places.

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 opens with 'Read contained records', which states the operation class but never names the resource being read — the agent must fall back on the tool name/title to learn these are availability records. It does distinguish the semantics from leave overlap, which is a useful differentiator against workfeed_list_leaves/workfeed_get_leave.

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?

Usage is only implied: 'This differs from leave overlap' signals that this tool is not for leave queries, but no sibling is named and no positive condition ('use this when you want WORK/NO_WORK blocks per employee') is given. An agent can infer the intent from the interval semantics but gets no explicit routing guidance among the 16 siblings.

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