Verify e-Service summary

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

The description discloses that the tool is unavailable until an adapter is implemented, which is a behavioral trait beyond the readOnlyHint annotation. However, it does not describe any other behavior or side effects, so it is only partially transparent.

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 and is concise, but it lacks the substance needed for a functional tool description. It is short but not appropriately informative.

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?

Given the tool's complexity (nested objects, required parameters) and lack of output schema, the description provides almost no context. It does not help an agent understand the tool's role or constraints.

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 description does not explain any of the parameters (employer, period) and the schema has 0% coverage in the description. The agent is left without any semantic understanding of the inputs.

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 states the tool is unavailable and provides no indication of what the tool does when implemented. The title hints at verifying a summary, but the description itself lacks a clear purpose.

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 given on when or how to use this tool. The only information is that it is unavailable, which does not help an agent decide to invoke it.

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