get_leave_transactions

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. Read-only intent is only implied by the 'get_' prefix; there is no mention of default date behavior, result ordering, pagination, or what a transaction record contains. Defaults for fromDate/toDate live only in 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?

It is a single short sentence with no padding, which is efficient, but the brevity comes from under-specification rather than disciplined editing. It reads as an incomplete fragment rather than a front-loaded statement of purpose.

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 simple two-optional-parameter read tool with no output schema and no annotations, the description should at minimum explain what a leave transaction is and how it differs from adjacent leave tools. As written, an agent cannot confidently decide between this and get_leave_requests or get_leave_balance.

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% and both parameters are optional, with the schema already documenting the YYYY-MM-DD format and the default values. The description adds nothing beyond that, so the baseline of 3 applies.

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 fragment names the resource (leave transactions) and scopes it to the signed-in employee, which loosely separates it from org-wide siblings. But it is a noun phrase with no verb, and it never clarifies what a 'transaction' is versus the sibling concepts get_leave_requests, get_leave_balance, and get_leave_stats. An agent can guess the topic but not the exact payload.

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?

There is no when-to-use guidance at all. With close siblings like get_leave_requests, get_leave_balance, and get_leave_stats in the toolset, the definition gives no condition, exclusion, or alternative to route between them.

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