Retrieve a security intelligence profile group by UUID to inspect its configuration and attributes. Use this to fetch specific SecIntel group details for policy or object management.
Get a SecIntel profile group object by UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description only says 'Get', implying a read operation, but does not disclose potential errors (e.g., not found), idempotency, or any side effects. For a simple get, this is minimal but acceptable.
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?
The description is a single, clear sentence with no unnecessary words. It is perfectly concise for a straightforward get-by-ID operation.
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 simple tool with one parameter and no output schema, the description is adequate but incomplete: it lacks parameter details, usage context, and return value description. It meets minimum viability.
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 description coverage is 0%. The description does not explain the 'uuid' parameter beyond its name, failing to add meaning to the input schema. The agent must guess the format or constraints.
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 the action (Get) and the resource (SecIntel profile group object by UUID). It distinguishes itself from sibling tools like sdcloud_get_secintel_profile (gets a profile) and sdcloud_list_secintel_profiles_groups (lists 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 guidance on when to use this tool versus alternatives (e.g., list vs. get, or profile vs. group). The agent is left to infer usage from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.