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

With no annotations, the description carries the full burden and does meaningful work: it discloses cost/auth ('Free, no API key') and the non-obvious semantics of industry_leader entries (doors verified open, no intent registered there), which prevents misreading the results. It stops short of describing result ordering, size, or whether the network list changes over time.

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, front-loaded with the resource and its definition before the status caveat and the cost note. The nested parentheticals ('an Outpost (a demand registry for brands with no agent door of their own)') are dense, but every clause contributes definitional content an agent would otherwise have to guess.

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-parameter list tool with no output schema, the description covers the key return semantics: brands plus per-Outpost status, and the special meaning of industry_leader. The absence of any mention of the response shape or how outposts map to the sibling tools keeps it just short of fully self-contained.

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?

Zero parameters, so the baseline applies; nothing about arguments needs explaining. The description correctly implies an unfiltered full-network listing with no arguments required.

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 ('List') and resource ('Agent Outposts network') and defines the domain term inline: brands with an Outpost, a demand registry for brands with no agent door of their own. The industry_leader status is explained concretely with examples (peetscoffee, kroger, bestbuy), so the agent knows exactly what this returns without opening any schema.

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: an agent can infer this is the discovery/enumeration tool for outposts, distinct from get_outpost_door_state or register_intent. But no sentence says when to prefer it over those siblings, and there are no explicit exclusions.

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