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

Beyond readOnlyHint=true, the description discloses the implicit status filter default, the 365-day range cap, the hub entitlement requirement, and the underlying endpoint. That is real behavioral context an agent needs to avoid silently missing pending/denied requests, though pagination and rate behavior are left to the schema.

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?

Three sentences, front-loaded with purpose and range constraint, then the default-filter caveat, then the access requirement. The long field enumeration is slightly run-on but serves as a return-value substitute given no output schema.

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, the description compensates by listing returned fields and clarifying the approved-only default; it also states the hub prerequisite and date-range limit. Nothing an agent needs to invoke this correctly is missing.

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 100%, so the schema already documents limit, offset, dates, statuses, and user_ids. The description restates the status default and the 365-day bound but adds no syntax or format detail beyond the schema, which is the expected baseline when structured fields carry the load.

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 and resource ('List time-off requests') plus the scoping semantics ('overlapping a date range'), and enumerates the returned fields, so it is clearly distinguishable from siblings like connecteam_list_time_off_policy_types. An agent knows exactly what this yields without opening the schema.

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?

Gives a concrete prerequisite ('Needs the HR & Skills hub') and a critical calling caveat ('returns only approved requests unless statuses is given'), which tells the agent when the default output is incomplete. It stops short of naming alternative tools or explicit when-not-to-use conditions.

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