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

No annotations are provided, so the description must carry the full burden. The description merely restates the tool's purpose ('get detailed information') without disclosing additional behavior such as read-only nature, return format, errors, or authentication requirements. The verb 'get' implies a read, but no extra context is added.

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 sentence, making it concise, but it essentially paraphrases the tool name/title without adding new information. It is not wasteful, but it fails to earn its place by providing any additional insight.

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 there is no output schema and no annotations, the description should explain what 'detailed information' includes or how the slug is obtained. The tool is simple, but the vague description leaves the agent without enough context, especially since sibling tools share a similar pattern.

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 documents the single parameter 'slug' with a clear description, so the description adds no extra meaning. With 100% schema coverage, the baseline is 3, and the description does not compensate or clarify beyond the schema.

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's function using the verb 'get' and resource 'hotel' (e.g., 'detailed information about a specific hotel'). It distinguishes from sibling tools like get_restaurant_details by targeting hotels, but does not explicitly mention the slug parameter or any unique scope, so it stops short of a 5.

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 when hotel details are needed, but it provides no explicit guidance on when to use it versus alternatives, no prerequisites (e.g., obtaining a slug from search_content), and no exclusions. It is not misleading, but the context is minimal.

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