global_groups_get_all

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

No annotations are provided, so the description carries full burden. While 'Get all' implies a read-only operation, it doesn't disclose important behavioral aspects like whether this returns a complete list or paginated results, potential rate limits, authentication requirements, or what format the data comes in. The description is minimal and leaves key operational questions unanswered.

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, efficient sentence that states exactly what the tool does without unnecessary words. It's front-loaded with the core functionality ('Get all global groups') and provides just enough context ('configured in ProPresenter'). Every word earns its place.

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 operation with no output schema, the description is adequate but minimal. It tells what the tool retrieves but doesn't provide context about the return format, data structure, or how this fits within the broader ProPresenter ecosystem. Given the complexity of the sibling tool list, more context about what 'global groups' represent would be helpful.

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?

With 0 parameters and 100% schema description coverage, the schema already fully documents the lack of inputs. The description appropriately doesn't waste space discussing parameters that don't exist, maintaining focus on the tool's purpose. This earns a baseline 4 since no parameter information is needed.

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 the action ('Get all') and resource ('global groups configured in ProPresenter'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'clear_get_groups' or 'props_get_all' that also retrieve collections, leaving some ambiguity about what makes 'global groups' distinct.

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 on when to use this tool versus alternatives. With many sibling tools that retrieve different types of data (e.g., 'playlists_get_all', 'themes_get_all', 'macros_get_all'), the description offers no context about when global groups are needed or what distinguishes them from other retrievable collections.

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