Refresh employers from e-Service

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

The description honestly discloses that the tool is not yet implemented, which is a key limitation. However, it does not describe what the tool would do if available or what happens upon invocation, leaving behavior largely opaque.

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, clear sentence with no wasted words. It directly communicates the unavailability status without unnecessary detail.

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?

The description lacks any context about the tool's intended function, such as what 'refreshing employers' entails or how it fits into the overall workflow. While the unavailability is stated, the missing purpose leaves the tool's role unclear.

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?

The tool has zero parameters and an empty schema, so there is nothing to describe. The baseline score applies because the description adds no parameter-related information.

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 only states that the tool is unavailable; it does not convey what the tool does or its intended purpose. An agent cannot determine what 'refresh employers' means or when it would be relevant.

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 is provided on when to use this tool, other than the implicit instruction that it cannot be used yet. There is no mention of alternatives or conditions for future use.

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