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

Annotations already declare this a safe, idempotent, open-world read, so the bar is lower; the description still adds costs-plus-terms framing and the fact that displayed prices are starting prices contingent on a checked quote, with no holder discount on Swarm Desk. The trailing 'Free.' is ambiguous (free call vs. free service) and slightly undercuts the payoff terms.

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?

Three compact sentences with the catalog scope front-loaded. The ending fragment 'Free.' is abrupt and ambiguous, and the Swarm Desk pricing detail is oddly narrow for a catalog-level description, but there is little outright waste.

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 parameters and no output schema, the description carries the load of telling the agent what comes back — per-service return values, USDC prices, holder terms, and x402 payment mechanics — and it does so in one sentence. That is sufficient for a zero-argument read-only catalog.

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 to disambiguate and the baseline applies. The description does not need to explain any 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 resource — the house services and crews price list — plus what it covers (return values, USDC prices, holder terms, x402 payment). It does not distinguish itself from siblings like nightshift_products, crews, or token_price, which could plausibly overlap, so differentiation is missing.

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?

Usage is implied rather than stated: read this to learn what house services cost before ordering or paying. The line 'requires a free checked quote for the exact price' implicitly routes the agent to swarm_quote, but no explicit when-to-use or when-not guidance is given relative to the overlapping pricing siblings.

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