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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavioral fact beyond that: every response carries pilot: true and a pilot-presence note, which tells the agent not to treat results as fully launched. It says nothing about ordering, volume, or what a café entry contains.

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 short sentences with no filler, and the pilot-status caveat is stated up front where an agent will see it. The terseness borders on cryptic, but nothing is wasted.

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 one-optional-parameter read-only list tool with no output schema, the description covers the pilot caveat but leaves the core question unanswered: what fields a hub/café record actually contains and what the list represents in the product. Adequate but with a clear gap for an agent deciding whether this tool answers its question.

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 coverage is 100% with a single optional 'city' parameter already documented as an optional city filter, so the schema does the work. The description adds no meaning about matching behavior (exact vs partial city names) or what happens when city is omitted, so baseline 3 applies.

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 as a 'Pack Hub café list,' which adds the word 'café' beyond the tool name, but it never states the action explicitly and never says what a Pack Hub is. An agent can infer 'list cafés' but gets no distinguishing detail against siblings such as list_missions or get_pack_board.

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 when-to-use guidance, no mention of when this tool is preferable to other pack-related tools, and no hint that the city filter is optional or when to supply it. The agent is left to infer usage entirely from the name.

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