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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds meaningful behavioral context beyond the annotations by specifying the return composition: headline stats, FAQ, offer, and the full page body rendered as Markdown. It does not contradict any annotations.

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 a single, information-dense sentence. It front-loads the key idea ('One service in full') and then immediately lists the exact contents returned, with no filler or repetition.

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 read-only, idempotent single-resource fetch, the description adequately covers what will be returned. Error behavior and response shape are not described, but with no output schema and a single required slug parameter, this is a minor gap rather than a critical omission.

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 provides 100% coverage for the only parameter, slug, with a clear example ('compliance' or 'graphql-architecture'). The description adds no additional parameter-level meaning, so the baseline of 3 for complete schema coverage 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 clearly identifies the resource ('one service') and the scope ('in full'), and enumerates the specific content returned: 'headline stats, FAQ, the offer, and the complete page body as Markdown.' This distinguishes it from list_services and other get_* siblings, which fetch different resources or list summaries.

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 phrasing 'One service in full' implies this is the tool to use when a complete single service is needed, but it does not explicitly state when to prefer it over alternatives such as list_services or search. There is no direct mention of exclusions or sibling routing, so usage guidance remains implied rather than explicit.

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