list-timeoff

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

No annotations provided; description fails to disclose key behaviors like pagination (despite schema having page and per-page), default sorting, or that it lists all entries (not scoped to current user). Agent lacks critical usage context.

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?

Single sentence of 13 words, no redundancy. Front-loaded with action and key features.

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 list tool with 7 parameters and no output schema, description is minimal. Doesn't mention pagination behavior, default values, or result format. Adequate but not comprehensive given complexity.

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 already covers all 7 parameters with descriptions. Description adds value by summarizing filter categories ('person, project, status, date range') but introduces error by saying 'project' instead of 'timeoff_type_id'. Marginal net benefit.

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?

Description clearly states the tool lists time off entries with optional filters, distinguishing it from get-timeoff or create-timeoff. However, it inaccurately mentions 'project' filter while schema has 'timeoff_type_id' for time-off type, which may cause confusion.

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 siblings like get-timeoff, get-person-timeoff-summary, or list-time-off-types. No when-not-to-use or alternative recommendations.

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