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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, static read profile is covered structurally. The word 'canonical' usefully signals an authoritative reference rather than live data, but the description adds no detail on freshness, rate limits, or return shape beyond that.

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 that leads with 'Canonical facts' and then lists contents. Every item earns its place by telling the agent what queries it can answer; it is slightly list-like but not padded.

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 params, no output schema, and annotations covering the read-only profile, the description's content enumeration is sufficient for an agent to call it and anticipate the result. The only missing piece is contrast with the sibling lookup tools.

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 empty schema is consistent with an all-facts-in-one-call design.

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 names a specific resource (canonical facts about Ashraf Gents Hostel) and enumerates the exact content returned: address, phone/WhatsApp, rooms, rates, rules, map position. An agent can immediately tell what it retrieves, though it draws no boundary against siblings like check_availability or nearby_places.

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?

It states what is returned but never says when to call this versus check_availability, nearby_places, or get_guide. No prerequisites, triggers, or exclusions are given, leaving the routing decision entirely to inference.

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