hcm_absence_balance

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

The readOnlyHint annotation already communicates that this is a safe read operation, and the description aligns with that by saying 'Search.' It adds the small detail that it targets Fusion planBalances, but it does not disclose what happens when no filters are provided, whether personNumber or finder is required, or how limit affects pagination.

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 a single sentence with no filler and the core action is front-loaded. However, it is so terse that it veers toward under-specification, offering little more than the tool name already implies.

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 search tool with four unannotated parameters and no output schema, the description is not complete enough for an agent to call it correctly. It leaves unanswered how to filter, what the response contains, and which parameters are actually needed.

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 0% and the description provides no meaning for q, limit, finder, or personNumber. With four undocumented parameters, the description was obligated to compensate but instead says nothing about how to construct a valid search or how the parameters relate.

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 names a specific action ('Search') and a resource ('absence plan balances'), and identifies the underlying Fusion planBalances source. It is not a tautology and an agent can tell the general operation, but it does not explicitly distinguish this from siblings like hcm_get_plan_balance or hcm_get_absence_type_balance.

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 guidance on when to use this tool versus alternatives such as hcm_get_plan_balance or hcm_search_absence_plans. No prerequisites, filters, or exclusion criteria are mentioned, so the agent must infer usage from the name alone.

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