ise_ers_get_sgt

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does (get by ID) but reveals nothing about response format, error handling for invalid/unknown IDs, authentication requirements, or whether the operation is read-only. For an ERS get operation the safety profile is implied by naming convention, but the description itself adds no behavioral context beyond the schema.

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 efficient sentence that fully conveys the tool's purpose. It's compact with no wasted words. However, given the complexity of the deployment parameter and the ambiguity around id semantics, additional brief context could be added without harming conciseness.

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?

There is no output schema and no annotations, so the description must carry more weight. For a get-by-ID tool, the description should at least note what happens for unknown IDs (error vs empty), and ideally document that SGT gets return the full SGT object. The sibling set includes ise_ers_list_sgt and ise_ers_search_sgt, so clarifying the distinction would improve completeness. The deployment parameter adds complexity that the description doesn't address beyond schema text.

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?

The schema documents the 'id' parameter (string, required) and the 'deployment' parameter with detailed semantics. The description adds the critical meaning of 'id' — it's the SGT ID used to fetch a specific object — and confirms the deployment targeting. Schema description coverage is 50% (deployment is well-described, id is not), and the description helps define what 'id' refers to. The deployment guidance (including referencing ise_list_deployments) is useful.

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 clear verb+resource pattern: 'Get a single Security Group Tags (SGTs) object by ID.' It clearly states the operation (get by ID) and the resource type (SGT). However, it doesn't differentiate from sibling tools like ise_ers_search_sgt or ise_ers_list_sgt, though the 'by ID' qualifier somewhat distinguishes it from list/search variants.

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 provides no guidance on when to use this tool versus alternatives like ise_ers_search_sgt or ise_ers_list_sgt. Sibling tools include list, search, and get variants for SGTs, but the description doesn't clarify the selection criteria (e.g., 'use this when you have an exact ID'). The deployment parameter schema does mention ise_list_deployments, but that's parameter-level guidance, not tool-level usage context.

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