umbrella_list_sites

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

No annotations are provided, so the description carries the full burden. It discloses that sites are logical groupings, which adds context, but it doesn't mention pagination behavior, response shape, or any filtering semantics. For a read-only list tool, the lack of behavioral detail beyond the resource definition is a gap.

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 a single sentence that front-loads the verb and resource, then adds a clarifying parenthetical. It is concise and every word earns its place, though it could have added a usage pointer without becoming bloated.

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 simple list tool with zero required parameters and full schema coverage, the description is mostly adequate. However, with no annotations and no output schema, it would benefit from a note about what a 'site' record contains or how paging works. The sibling context helps disambiguate, but the description alone leaves some context gaps.

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 100%, so the schema already documents limit, offset, and additionalParams. The description adds no parameter-specific meaning beyond the schema, which is acceptable given full coverage. The additionalParams escape hatch is well-documented in the schema itself.

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 states a specific verb ('List') and resource ('Umbrella sites') and clarifies what sites are ('logical groupings of virtual appliances/internal networks'). This distinguishes it from siblings like umbrella_list_networks and umbrella_list_virtual_appliances, though it doesn't explicitly name them.

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 this is for listing site groupings, and the sibling list shows related list tools, but there is no explicit when-to-use guidance or exclusions. An agent can infer usage from the resource definition, but the description doesn't state when to prefer this over umbrella_list_networks or umbrella_list_virtual_appliances.

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