get_service_metrics

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

With no annotations provided, the description carries the full burden. It clearly implies a read-only operation via 'Get' and explains the discovery purpose, adding context that this is a prerequisite before data retrieval. However, it does not disclose potential side effects, permission requirements, or return format details, so it is slightly limited but adequate for a simple read tool.

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 concise sentences deliver the purpose and usage guidance without any fluff. Every word contributes meaningful information, making it efficient and well-structured.

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?

Despite having no output schema, the description adequately conveys the return value (a list of performance metrics) and its role in the workflow. The description is sufficiently complete for a simple discovery tool with well-documented parameters.

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 fully describes both parameters (host_id and service_id) with clear descriptions ('Centreon host ID' and 'Centreon service ID'), achieving 100% schema coverage. The description adds no additional parameter semantics, but the baseline of 3 is appropriate given the schema's completeness.

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 clearly states the tool retrieves a list of performance metrics for a specific service, using the specific verb 'Get' and resource 'performance metrics.' It also distinguishes itself from sibling tools by positioning this as a discovery step before fetching time-series data, implying differentiation from get_metrics_data.

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?

Explicitly instructs the user to 'Use this to discover metric names before fetching time-series data,' providing clear context on when to invoke this tool. It implicitly indicates not to use it for fetching actual data, which is a separate step, and the sibling list supports the alternative.

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