Create Leave Request

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

Annotations indicate a mutating operation (readOnlyHint: false) but not destructive. The description adds that status starts as 'pending' awaiting approval. However, it does not disclose other side effects like notifications or required permissions. Given minimal annotations, the description adds moderate value.

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 two sentences in English and Spanish, conveying essential info efficiently. The bilingual content is somewhat redundant but does not harm clarity. It is front-loaded with the main action.

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 straightforward creation tool, the description covers purpose, types, date format, and initial status. It does not explain return values (though output schema exists), error handling, or prerequisites, but remains adequate given the tool's simplicity.

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%, so the schema already documents all parameters. The description reiterates the date format and lists types, but adds little beyond what the schema provides. Baseline 3 is appropriate as the description does not significantly enhance parameter understanding.

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 explicitly states 'Create a new leave/PTO request for an employee.' It mentions specific leave types, date format, and initial status, clearly distinguishing it from sibling tools like leave_approve, leave_cancel, leave_list, and leave_reject.

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 provides context on leave types and date formatting, but fails to specify when to use this tool versus alternatives (e.g., when to create vs. list or approve requests). It does not offer explicit usage or exclusion criteria.

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