Site: List_site_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read against live data. The description adds the site-scoping constraint but says nothing about pagination, result volume, or return shape, so it contributes only modest context 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?

A single efficient sentence with the resource front-loaded and zero filler. It is appropriately sized for the tool's simplicity, though it is minimal enough that it could afford one more clause of guidance.

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 single-parameter read-only list tool with full schema coverage and annotations declaring the safety profile, the description is adequate. No output schema exists, so return values need not be explained; the only soft gap is the absence of pagination or scoping caveats.

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?

There is a single parameter (siteId) with 100% schema description coverage, so the schema already carries the semantics. The description adds no format, type, or constraint detail beyond 'associated with a site', making this a baseline case where structured data does the work.

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 (List) and resource (access groups) with clear site scoping. It distinguishes itself from the sibling site-scoped lists (List_site_access_points, List_site_cameras) by naming 'access groups', though it does not explicitly separate itself from Group: List_groups at the account level.

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 by the name and description - list groups for a given site - but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as Group: List_groups or List_group_users. The site-scoping is the only routing signal.

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