check_service

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the side-effect-free mechanics (WSDL fetch + port binding vs. base_url request) and the null-service default of checking everything. It stops short of saying what the check returns on failure or whether it retries, but with annotations present the bar is lower.

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?

Two tight sentences with the core definition front-loaded and the default-scope rule following. 'REST requests base_url' is compressed almost to the point of ambiguity (GET? HEAD? timeout?), which is the only thing keeping it from a 5.

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 values need not be described, and the mechanics are covered. But with 0% schema coverage, the undocumented 'environment' parameter is a real completeness hole for a tool whose whole job is scoped connectivity testing.

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%, so the description must carry the load, yet it only explains one of two parameters: 'service' (omitted = check all). The 'environment' parameter is never mentioned anywhere, leaving an agent to guess what values it accepts or what it scopes. This is a clear compensation gap.

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 specific verb+resource ('connectivity check') and immediately scopes it as 'without calling an operation', which separates it from soap_call/rest_call siblings. It also explains the per-protocol mechanics (SOAP loads WSDL and binds port, REST hits base_url), so an agent knows exactly what kind of check this is. It never names a sibling explicitly, keeping it short of a 5.

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?

'Without calling an operation' implicitly tells the agent to use this for validation rather than invocation, and 'Without service every service is checked' clarifies the sweep behavior. However, it never states when to prefer this over just calling soap_call/rest_call, nor any prerequisites or exclusions.

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