create_leave_period

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

Adds real behavioral context beyond the annotations: the refusal rule when time is already declared over those days, and that delete_declarations removes that time irreversibly. There is a mild tension with destructiveHint=false, since a conditional irreversible deletion is disclosed, though it defaults to false — the description is more informative than the hint, not contradictory, but the mismatch is worth noting.

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?

Front-loaded with purpose, then alternative routing, then the half-day encoding rule, then the destructive caveat. Four dense sentences with no filler; each clause carries distinct information.

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?

Output schema exists, so return values need no explanation, and the mutation semantics are well covered. Remaining minor gaps: no indication of permission requirements for declaring leave on behalf of another user, and no date/timezone format hint for start_at, though the schema carries the parameter-level detail.

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 baseline is 3, but the description adds non-obvious semantics: the half-day encoding rule ('a single afternoon off is the same day twice, pm to pm') and the consequence of delete_declarations in relation to the refusal behavior. Those are genuinely useful beyond the per-property descriptions.

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 ('Declare a leave period (days off) for a user'), including the default scope ('the current one by default'). It immediately separates itself from update_leave_period and list_leave_periods, so an agent can route without opening sibling schemas.

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?

Explicitly says when to use it ('for holidays and absences') and names the two most confusable alternatives with their selecting conditions: update_leave_period to move an existing one, list_leave_periods to check existing ones first. That is exactly the routing guidance an agent needs before calling a create tool on a resource that can conflict with existing data.

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