zid_get_group

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

Annotations already declare readOnlyHint=true, so the description's mention of 'Read-only' is redundant. No additional behavioral traits (e.g., auth requirements, rate limits) are provided beyond the annotations.

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 short sentences are well front-loaded and concise. However, the second sentence 'Read-only.' is redundant given annotations, so one sentence could suffice.

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?

The tool is simple with one parameter, but the description does not mention what the response contains (e.g., group details). Since there is no output schema, a brief note about the return structure would improve completeness.

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% schema description coverage, the description should add meaning to 'group_id', but it only says 'by ID', which is a minimal rephrasing of the schema. No extra context like format or source of the ID is given.

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 uses a specific verb ('Get') and resource ('ZIdentity group by ID'), clearly distinguishing it from sibling tools like 'zid_list_groups' (lists all groups) and 'zid_search_groups' (search-based retrieval).

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 implicitly states when to use: when you have a specific group ID. It does not explicitly exclude alternatives (e.g., searching by name), but the simplicity of a get-by-ID makes the context clear.

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