Get service

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

No annotations are present, so the description carries the behavioral disclosure burden. It does add a concrete trait by stating 'No API key required,' and 'Get details' conventionally implies a read-only operation. However, it does not disclose whether any other authentication is needed, how unknown slugs are handled, or whether the operation has any side effects.

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 two short sentences with zero filler. The core operation is front-loaded, and the 'No API key required' statement earns its place by giving an essential invocation detail.

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?

For a one-parameter read tool with no output schema and no annotations, the description is mostly complete: it identifies the input format and the no-key requirement. The only gaps are explicit return-value details and error behavior, but these are minor for such a simple operation.

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 schema already fully documents the single 'slug' parameter with the same explanation (SEO slug or service code) and examples. The description adds no parameter-level meaning beyond what the schema provides, so the high schema coverage baseline of 3 is appropriate.

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 a specific verb ('Get'), a precise resource ('details for a single service'), and the lookup key format (SEO slug or service code). 'Single service' clearly distinguishes it from list_services and get_service_countries, making its purpose unambiguous.

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?

The description implies usage: to retrieve details for one service, but it does not explicitly compare against siblings like list_services or get_service_countries, nor does it give conditions for choosing this tool. The 'single service' wording is enough for an agent to infer its niche, but there is no direct when-to-use guidance.

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