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

No annotations are provided, so the description bears the full burden. It clearly states that the tool performs a listing operation, which implies read-only behavior. It does not disclose details like output shape, ordering, pagination, or whether offers are full objects or summaries, but these are not critical for a simple zero-parameter list.

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?

A single, dense sentence that leads with the action and resource, followed by the key qualifier about offers. No filler or redundancy; every word adds meaning.

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 tool with no parameters and no output schema, the description provides enough for an agent to invoke it: it states the domain (ANAMIZED systems) and the expected content (systems and their offers). It does not explain the format of the offers or the meaning of 'ANAMIZED', but those details would not prevent a correct call.

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 has zero parameters, and with schema coverage at 100% (vacuously), there is no parameter information for the description to augment. The baseline of 4 applies, and the description needs no further parameter detail.

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 uses a specific verb ('List') and identifies a clear resource: ANAMIZED systems, enumerating the concrete system families (YodMCP, OpenGOS, RUI, Edge-OS, kernels) and their offers. This makes it easily distinguishable from sibling list tools like list_agents or list_offers by scope alone.

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?

The description implies usage: when you need to see systems and their offers. However, it does not explicitly state when to use this over alternatives such as list_offers or list_mcp_servers, nor does it mention any exclusions or prerequisites. Usage context is inferred rather than stated directly.

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