Ping midPoint

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

With no annotations, the description carries the full burden; it does disclose that the call is a GET against /ws/rest/self, which implies a safe read and reveals the auth surface (the response reflects the caller's authenticated identity). It does not state whether it requires authentication to succeed, what happens when midPoint is unreachable, or whether it has side effects — meaningful gaps for a health-check tool with zero annotation coverage.

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 operational sentence is front-loaded and efficient, and the endpoint reference is a useful concrete anchor. The trailing sentence about display names versus OIDs is unearned for this tool — it is irrelevant to a parameterless ping and dilutes focus, though the overall length remains short.

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?

An output schema exists, so return-value explanation is not required, and with zero parameters the surface is simple. The definition is nonetheless incomplete in a way that matters: the sibling whoami is an apparent duplicate and nothing here tells the agent which to prefer, and the misplaced write-guidance sentence suggests boilerplate rather than deliberate scoping.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description adds nothing that could conflict with the empty schema.

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 concrete verb+resource: check connectivity to midPoint and report the authenticated identity, reinforced by naming the underlying endpoint GET /ws/rest/self. It does not, however, distinguish itself from the sibling whoami tool, which on its face appears to return the same identity information, leaving the agent to guess which to call.

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 versus whoami, which is the obvious alternative for identity lookup. The second sentence ('When you write to a person, name people, roles and requests by their display names rather than OIDs') is usage guidance for write tools like create_user or assign_role, not for a zero-parameter connectivity check, so it provides no applicable routing help here.

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