get_groups

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

No annotations are provided, so the description carries full burden. It states 'Read-only', which is useful, but omits return shape, pagination, auth requirements, and side-effect details. 'SOAP operation: GetGroups' is redundant with the first sentence.

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?

Three fragments where one would do; the first and third sentences say essentially the same thing ('Calls GetGroups' / 'SOAP operation: GetGroups'). The one piece of real information ('Read-only') is buried mid-sentence.

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-arg retrieval tool with no annotations and no output schema, the description should describe what is returned (group shape, count, filtering behavior). Instead it repeats the operation name and offers no behavioral or return information.

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?

Zero parameters is a baseline 4. There are no parameters to document, so nothing is missing on this dimension.

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 verb ('Calls') and resource ('GetGroups') but the resource name is just the operation identifier repeated, not a plain-language description of what the tool returns. It doesn't distinguish itself from the sibling 'list_groups', which likely serves a similar or identical purpose. The purpose is only implicit: it retrieves groups.

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 when-to-use guidance, no explicit alternatives. A sibling named 'list_groups' exists and the description gives no information on how this differs or when to prefer one over the other, leaving the agent to guess between two similarly named tools.

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