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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond them: the authentication requirement (owner sign-in) and the fact that the response includes a test-mode flag, which an agent should know before trusting the data.

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?

A single front-loaded sentence identifies the resource, then enumerates the returned fields, then states the auth prerequisite. Every clause carries information; nothing is redundant with the title or annotations.

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?

With no output schema, the field enumeration does the work of describing the return payload, and the auth requirement is disclosed. It stops short of covering edge behavior, such as what happens if the owner has no hotel configured or whether more than one hotel can be returned.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is fully closed (additionalProperties=false) and consistent with the no-argument description.

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 hotel's details" names a specific resource and the enumeration of fields (name, address, phone, rooms, check-in/check-out, taxes, test mode) makes the retrieval concrete. It does not distinguish itself from siblings like house_inventory or setup_status, but the read-the-hotel-record purpose is 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?

Usage is implied rather than stated: the agent can infer this is the call for the current hotel's profile, and the note that it "needs the owner's sign-in" is a useful prerequisite. However, there is no explicit when-to-use/when-not guidance and no routing to alternative siblings that also surface property information.

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