duo_get_group

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

No annotations are present, so the description carries the full behavioral burden. It says 'Get full detail' but provides no details about response content, error cases, permissions, or side effects. 'Full detail' is vague and does not add meaningful behavioral context beyond the action of getting.

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?

One short sentence, front-loaded with verb and resource, no wasted words. It is appropriately sized for a simple single-parameter getter.

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?

With no output schema and no annotations, the description should clarify what 'full detail' means. It does not specify return fields or behavior on missing/invalid IDs. The description is adequate for a trivial tool but leaves ambiguity about the response shape.

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 100% (groupId, string, 'Duo group_id'), so the baseline is 3. The description restates 'by group_id' but adds no new semantics about the parameter's format, source, or constraints. It does not compensate or expand beyond the schema.

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 'Get full detail for a single group by group_id' – a specific verb (get), resource (group), and identifier (group_id). This clearly distinguishes it from sibling tools like duo_list_groups (lists all groups) and duo_list_group_users (lists members of a group). The purpose is unambiguous.

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 gives no when-to-use guidance. It does not mention alternatives such as duo_list_groups for browsing groups or duo_list_group_users for membership. An agent must infer from the name that this retrieves a specific group; no explicit selection criteria or exclusions are provided.

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