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

Beyond the readOnlyHint/openWorldHint=false annotations, it discloses that the full list returns in one call with no paging or server-side search, and that deleted outlets are excluded. It also states negative facts (no opening hours, timezone, currency, or per-outlet tax) and where the tax data actually lives — the kind of non-obvious behavior an agent cannot infer from the schema.

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?

Front-loaded with the core definition before the ID-resolution guidance and negative disclosures, with every sentence earning its place. It runs long and the capitalized emphasis is somewhat shouty, but it remains structured and skimmable rather than 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?

For a no-parameter, no-output-schema list tool the description covers everything an agent needs: what it returns, paging/search behavior, deleted-record handling, the ID-resolution role relative to sibling tools, and explicit boundaries on adjacent data (hours, currency, tax).

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 per the rubric the baseline is 4. The description appropriately adds no parameter detail because there is nothing to document; its filtering guidance concerns the returned list, not inputs.

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 ('Every point of sale (store, location, branch) the merchant has') and anchors it to a familiar UI surface (Settings → Outlets). It is clearly distinguishable from the sibling mutation tools hub_create_outlet, hub_update_outlet, hub_delete_outlet and hub_import_outlets, and it gives concrete example queries it answers.

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?

Explicitly routes the agent: reports, inventory and station tools filter by outlet ID and never by name, so this must be called FIRST to resolve a store name into an id. It also names the constraint (no server-side search, match the name yourself) and tells the agent what not to guess at.

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