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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine non-obvious behavior beyond that: a missing listing does not cause creation or endorsement, i.e. no upsert side-effect. It still does not say whether a miss yields an error or empty result.

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 zero waste; the accepted identifier formats are front-loaded and the not-found caveat follows. Nothing extraneous.

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-parameter read tool with annotations covering safety and no output schema, the description covers accepted input forms and the key not-found behavior. The only gap is the on-miss return/error shape, a minor omission.

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 description coverage is 0% for the single generic 'reference' parameter, so the description must compensate. It does, by specifying that the value may be an ID, a slug, or a GitHub repository URL, which is exactly the missing semantics.

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 (Read) and resource (a published listing), and enumerates the accepted identifier forms (ID, slug, GitHub repo URL). It clearly reads rather than mutates, implicitly separating it from register_swarm/update_swarm, but it never names a sibling.

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: read a listing when you already have an identifier. There is no explicit guidance on when to use this versus search_swarms (which obviously handles query-based lookup) and no stated exclusions or prerequisites.

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