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

Annotations already declare this as a safe, read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds only the word 'Live', which hints at real-time freshness but does not explain what is returned, how current it is, or how the topology is scoped. With zero annotation burden remaining, this is a very thin contribution.

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?

The description is only four words and is front-loaded, so it is not bloated. However, its brevity comes from under-specification rather than discipline: it omits the verb and the return semantics that would let an agent act on it.

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?

There is no output schema, no parameters, and only four words of description, so the description must carry the full burden of explaining what the tool produces. It does not say whether the result is a node list, edge list, or rendered graph, nor what 'live' means in terms of freshness. For a zero-argument read tool in a crowded agents_* namespace, this leaves a material gap.

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 for the description to disambiguate, and the baseline for a parameterless tool applies. Schema coverage is 100% by default because the input is an empty object.

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 'Live swarm topology' largely restates the tool name and title rather than stating a specific action or defining what 'topology' contains. It gives no verb and no indication of whether it returns a graph, a list, or a snapshot of agent relationships, so an agent cannot distinguish it confidently from siblings like agents_reputation or trust_score.

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?

There is no guidance on when to call this tool, what question it answers, or which sibling to use instead for related agent-state queries. The only implied usage comes from the words 'live' and 'topology', which is not enough to route between the many agents_* and trust_* alternatives.

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