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

With readOnlyHint=true and openWorldHint=false already declared, the safety profile is covered by annotations. The description adds the useful fact that this is a broad static-info retrieval, but says nothing about response shape, caching, or whether the answer is canned vs. assembled.

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, no filler; the content scope comes first and the call-first instruction is front-loaded last as the actionable cue. Every clause earns its place.

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?

For a zero-required-param overview tool with annotations covering safety and no output schema, the enumerated coverage list effectively stands in for a return-value description. Only minor gaps remain, such as whether the overview can be narrowed by topic.

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?

Schema description coverage is 100% and the single lang parameter already documents its enum and the 'use the user's language' rule, so the schema carries the burden. The description does not mention lang at all, adding no meaning beyond structured data — baseline 3.

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 the resource (Hilo Studio) and enumerates the exact content covered — what it does, location, languages, how it works, awards, contact. That is far more specific than a tautology, but it never explicitly contrasts itself with siblings like hilo_get_service or hilo_get_pricing, so an agent must infer the boundary.

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?

'Call this first for general questions' is an explicit routing rule that tells the agent when this tool wins over the more specific get_/list_ siblings. It stops short of stating when NOT to use it (e.g. for a single service or post), so it is clear context without explicit exclusions.

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