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

No annotations are provided, so the description carries the behavioral burden. It clearly discloses that this is a read operation returning a comprehensive bundle, including 'full page text as markdown,' which is a meaningful behavioral detail. It does not discuss potential errors, rate limits, or permissions, but for a simple getter these are less critical.

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 sentences, no filler. The first sentence front-loads the core behavior and return contents; the second provides usage context and the source for the slug. Every clause earns its place.

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 single-required-parameter read tool with no output schema, the description fully explains what the agent will receive: description, page markdown, FAQs, case studies, pricing, and timeline. It also gives the prerequisite step (list_services) and the usage trigger, making the tool complete from an agent's perspective.

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 coverage is 100% with a clear example in the schema. The description adds extra value by instructing the agent to obtain the slug from list_services, which clarifies where the parameter value comes from. This goes beyond the schema's static definition.

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 ('Returns') and resource ('everything the site says about one service'), then enumerates exact content types: description, markdown page text, FAQs, case studies, and pricing/timeline. This clearly distinguishes it from sibling tools like get_pricing, get_faq, or get_case_study by framing it as the composite service-detail endpoint.

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 explicitly says when to use it: 'when a user asks what a specific service involves or whether it fits their need.' It also tells the agent to get the slug from list_services. It does not explicitly name sibling tools that should be used instead for narrower questions, but the when-to-use guidance is clear.

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