mixer_group_info

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

No annotations provided, so description carries the burden. It states it's a read operation ('Get') and lists returned fields, but doesn't mention error behavior or that it doesn't modify state. However, given it's an info retrieval, the read nature is implied.

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?

Two concise sentences with purpose and args. No fluff.

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?

Simple read tool, description lists output fields API is straightforward. Could mention error cases or relationship to mixer_group_list, but not necessary for a simple query.

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 has only type string, no help. The description adds that target is 'Group path or {guid}', which clarifies acceptable formats. This is useful 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?

The description clearly states it retrieves a mixer group's guid, name, path, and volume, using a specific verb ('Get') and a specific resource (mixer group). It distinguishes from siblings like mixer_group_list (listing) and mixer_group_route (routing).

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 purpose implies usage (fetch info about a single group) but provides no explicit when-not or alternative guidance. Sibling tools like mixer_group_list suggest alternatives, but the description doesn't clarify when to use this vs. listing all groups.

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