list_networks

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds only the endpoint line and no further behavioral context such as authentication expectations, pagination, or result scope, so it earns limited credit beyond the annotations.

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 very short and front-loaded, with no filler; the first line states the action and the second line gives the exact endpoint. It is appropriately sized for a zero-parameter read-only tool, though it sacrifices detail for brevity.

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, read-only endpoint, the definition is mostly complete: output schema covers return shape and annotations cover safety. However, it leaves the domain meaning of 'networks' unstated and gives no selection context, so an agent may not know when this is the appropriate tool.

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 input schema has zero properties, so there is no parameter meaning to add. With 100% schema coverage and no parameters, the description cannot be penalized for missing parameter documentation.

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 names the exact action and resource ('Get networks') and gives the raw endpoint ('GET /networks'). It is unambiguous enough to distinguish from the many list_* siblings because there is no other networks-specific tool, though it does not elaborate on what a 'network' is.

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 guidance is provided about when to call this tool versus alternatives or what kind of task it supports. The description simply restates the action; there is no mention of use cases, prerequisites, or exclusions.

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