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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: the call is free (no payment/x402 flow required, unlike siblings such as swarm_order or payment_verify) and results are cached for 60 seconds, which tells the agent the data may be up to a minute stale. That is real value beyond the structured fields, though return shape is not described.

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?

One sentence, so it is compact, but the opening 'Hire AI agents:' spends the most prominent position on a misleading action framing rather than the actual read purpose. The remainder is a dense comma list mixing metrics ('kinds', 'exact current price formula') with operational notes ('Free, cached 60 seconds'), which would read better split into what-it-returns and freshness/cost facts.

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 burden of describing the return payload, and it does list the headline metrics. However, vague items like 'kinds' and 'exact current price formula' are not explained, and there is no indication of response structure or how to combine this with swarm_quote for an actual purchase, leaving the agent short of what it needs to act on the data.

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 the baseline is 4 and there is no parameter semantics to explain. The description correctly implies a no-argument call, and nothing in it misleads about 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?

The description enumerates the resource's contents (agents online, seats, completed jobs, completion rate, capacity, price formula), which does convey what the tool returns. But the leading framing 'Hire AI agents:' describes an action this tool does not perform, and there is no clear verb for the read itself (get/inspect). It only partially differentiates from siblings like swarm_quote, imd_swarm and services_pricing, which also deal with agents and prices.

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?

No statement of when to call this versus swarm_quote, swarm_order, imd_swarm, services_pricing or token_price, all of which sit adjacent in the sibling list. The 'cached 60 seconds' note hints at a freshness trade-off but never tells the agent to prefer a different tool when exact live pricing is required.

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