get_vulnerability_group

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing further — it never says what 'full details' comprises, whether related findings/CIs are included, or what happens if the identifier is unknown or malformed.

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?

A single front-loaded sentence with no filler; the identifier and example are packed into the same clause as the action.

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 one well-documented parameter and no output schema, the definition is serviceable but thin — 'full details' is left unexpanded, and for a read of a vulnerability record an agent would benefit from knowing the shape of the response.

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% and the schema already documents both accepted forms (VULxxxxxxx or 32-char sys_id). The description's example 'VUL0000103' is illustrative but largely redundant with the schema text, so it lands at the baseline.

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 specific verb (Get) and resource (Vulnerability Group) with single-record scope, and names the accepted identifiers. It is clear enough to separate from list_vulnerability_groups, though it never explicitly names that sibling or its create/update counterparts.

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?

Usage is only implied: fetch one record when you already know its VUL number or sys_id. There is no explicit guidance on when to prefer this over list_vulnerability_groups or update_vulnerability_group, and no preconditions stated.

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