get_service

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

No annotations are provided, so the description must carry behavioral context. 'Get' signals read-only, and 'full details' indicates a comprehensive return, but it doesn't disclose error behavior, required permissions, or any side effects. This is a moderate gap for a getter.

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?

One sentence of only 14 words, front-loaded with the verb and resource. Every word adds essential meaning; no fluff.

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 absence of an output schema, the description doesn't clarify the return structure. It adequately explains the tool's core function but omits behavioral details like error handling or whether service_id is globally unique. For a simple getter with fully documented parameters, it's acceptable but not rich.

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 input schema already describes both parameters as 'Centreon host ID' and 'Centreon service ID'; the description's 'by host ID and service ID' adds no new semantics. Schema coverage is 100%, so baseline 3 applies.

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 'Get full details for a specific service by host ID and service ID,' which clearly identifies the action (get), resource (service), and selection criteria. It distinguishes from siblings like list_services (listing) and get_host (different resource).

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 explicit when-to-use or alternatives are given. The phrase 'specific service' implies you should use this when you have a known host_id and service_id, versus list_services for browsing. However, it doesn't name alternatives or exclusions.

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