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

Annotations declare readOnlyHint and openWorldHint, and the description adds genuine behavioral context beyond them: the artifact produced is a message, the user must send it, and confirmation comes from the hostel. It also states a subject restriction ('Men only') absent from the schema. Return content/format is not described, keeping it below 5.

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?

Three short sentences, front-loaded with what the tool does, followed by the most important negative constraint and the eligibility restriction. No filler.

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 no output schema and a deep non-booking constraint, the description covers purpose, boundary, and eligibility well. The remaining gap is parameter meaning for a 6-param tool, which is only partially handled by the schema.

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?

Six parameters with only 50% schema description coverage, and the description explains none of them. Semantics for length (nights vs months), purpose, and guests must be inferred entirely from the schema, and 'Men only' is not mapped to any parameter.

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?

States a specific verb and resource ('prepares a WhatsApp message to Ashraf Gents Hostel asking whether a bed is free') and immediately disambiguates scope by ruling out booking. An agent can distinguish this from get_guide, get_hostel_facts, and search_guides without opening any schema.

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 states what the tool does NOT do ('does NOT book or reserve anything; the user must send the message and the hostel confirms'), which defines the boundary against a hypothetical booking sibling. It does not name any actual sibling alternative, so it falls short of a 5.

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