ise_openapi_radius_condition_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it provides almost none. It doesn't state whether this is read-only, whether authentication/permissions are required, what happens on invalid/missing id (404?), or what the response shape looks like. 'Returns a library condition' gives no behavioral detail beyond the operation itself.

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 one sentence plus the endpoint reference. It's compact and front-loaded with the domain label. However, the brevity works against it since the space isn't used to add helpful behavioral content. Still, conciseness itself is appropriate—no wasted words.

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 GET-by-id tool with no output schema and minimal annotations, the description should explain what a library condition is, what the returned object contains, and how it differs from other condition tools. None of this is provided. This is a moderate-complexity tool (ISE policy conditions) whose documentation is too thin to fully guide an agent.

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?

Although schema description coverage is 100%, the descriptions are nearly empty: 'Path parameter id' adds no semantic meaning about what the id represents or its format. The deployment parameter is well documented (name/slug/number syntax with an explicit example), but the primary 'id' parameter that selects the condition receives zero semantic context beyond being a path parameter.

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 states it 'Returns a library condition' for Network Access via a specific API endpoint. It identifies the resource (library condition) and the operation (get/return) clearly. However, it doesn't differ from sibling ise_openapi_radius_condition_create/list, and it doesn't clarify what a 'library condition' is or how it distinguishes from tacacs_condition. The purpose is clear but lacks sibling differentiation.

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 this is for fetching a single condition by its id. It provides no explicit when-to-use guidance, no exclusions, no mention that the id must already exist or how it relates to the condition_list tool. It does not contrast with ise_openapi_radius_condition_list or the create variant, so usage context is only implied.

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