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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral note — that the content is official business information and not an independent ranking — which sets expectations about source and bias. It says nothing about caching, freshness, or whether hours can be stale.

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, front-loaded with the primary purpose and followed by the scope disclaimer. The content enumeration is dense but each item earns its place by telling the caller what comes back.

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 and no parameters, the description carries the whole burden of describing the response, and it does enumerate hours, phone, directions, facilities, breakfast listings, reservation links, and price examples. What is missing is routing guidance relative to the three sibling 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 are no parameter semantics for the description to clarify; the baseline for a no-param tool applies. The enumerated content list usefully tells the agent what it will receive in place of any arguments.

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 ('Get a source-backed bilingual introduction to Bashoor Cafe'), with real substance about what the payload contains. It does not, however, differentiate itself from the sibling get_business_profile, which plausibly covers overlapping business information.

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?

There is no statement of when to call this versus get_business_profile, get_menu, or search_menu, even though get_menu and this tool both touch breakfast listings and prices. An agent must guess which entry point to use.

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