list_catalog_groups

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

No annotations exist, so the description must bear the burden. It discloses pagination behavior and return format, plus group ID uniqueness. However, it does not explicitly state that the operation is read-only or non-destructive.

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 moderately sized and front-loaded with the main purpose, but the Args section follows a docstring style that adds verbosity without additional value. Could be more streamlined.

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?

Covers purpose, parameters, and return format. However, it lacks usage guidance and does not explain how groups relate to controls (sibling tool list_catalog_controls). The description is adequate but not fully complete for a nuanced hierarchy.

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 coverage is 0%, but the description explains all three parameters: parent_doc_uuid scopes to a catalog, offset is zero-based, limit is max 1-100 with defaults. This adds meaning beyond type/default alone.

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 clearly states 'List groups within OSCAL Catalog documents' and explains that groups organize controls into families with unique IDs. This distinguishes it from siblings like list_catalogs and list_catalog_controls.

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 on when to use this tool versus alternatives like list_catalogs or list_catalog_controls. The description mentions parent_doc_uuid for scoping but does not set context or exclusions.

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