ise_ers_get_guestuser

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

No annotations are provided, so the description carries full burden. It states the get operation but discloses nothing about behavior: no indication this is a read-only/safe operation, no mention of what happens for a non-existent ID (404 vs empty), no authentication/permission requirements, no pagination. For a single-object retrieval tool with zero annotation coverage, this is a meaningful gap.

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 concise sentence that states the action clearly. There's zero waste. It could add a note about the Guest User resource naming, but at 10 words it is appropriately lean given the schema already documents the deployment parameter thoroughly.

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?

This is a simple read tool with 2 params and no output schema, so complexity is low. However, with no annotations, no output schema, and a minimal description, the agent lacks context about what a Guest User object contains, error behavior, or permission requirements. The deployment parameter compensates somewhat via schema, but the overall picture is thin for a tool operating in a system as complex as ISE ERS.

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 50%. The description adds the semantic 'by ID' for the id parameter, which is implied but useful. The deployment parameter is fully documented in the schema itself with rich guidance (name/slug/number, default behavior, which tool to call for choices), so the description needn't add more. The id parameter's meaning is adequately conveyed by the name and description, keeping this at baseline 3.

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 'Get a single Guest Users object by ID' uses a specific verb (get), names the resource (Guest Users object), and specifies the accessor (by ID). It clearly distinguishes from the 'list' and 'search' siblings which retrieve multiple objects. However, it doesn't highlight the distinction that guests are named 'Guest Users' (plural) in ERS terminology, which is minor.

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 implies usage: when you already have a guest user's ID, use this to fetch a single object. The sibling set makes clear that 'list' returns all and 'search' queries by attribute, so get-by-id is implicitly different. However, there's no explicit when-to-use vs alternatives, no mention that it requires a known ID (as opposed to search by name), and no guidance distinguishing it from ise_ers_search_guestuser.

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