ise_openapi_radius_condition_list

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. It fails entirely here: it doesn't mention return format, pagination behavior beyond the schema's page/size defaults, result ordering, whether conditions are filtered by policy type, or whether the 'library' restrictions are system-defined vs user-defined. For a list endpoint with zero annotation coverage, this is a significant 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 plus an endpoint reference. It's front-loaded with the main purpose. No wasted words, though it could add more behavioral detail without becoming verbose.

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 list tool with no output schema and no annotations, the description is thin. It doesn't describe what condition objects look like, how many can be returned, response structure, error conditions, or how 'library' conditions differ from policy-specific ones. A more complete description would explain the returned condition schema and any constraints on the list operation.

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 33% (only the deployment parameter has a description). The page and size parameters are bare integers with defaults but their semantics (pagination) are self-evident from names. The deployment parameter has a thorough description explaining accepted formats, which adds value. Overall the description adds marginal value beyond the schema for only one of three parameters.

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 all library conditions for Network Access policy (GET /api/v1/policy/network-access/condition). The verb 'returns' plus resource 'all library conditions' is reasonably clear, but the term 'library conditions' is domain-specific and not explained. It distinguishes from siblings like radius_condition_get (single fetch) and tacacs_condition_list (TACACS variant) via the Network Access qualification, but only weakly since it doesn't name alternatives.

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?

There is no guidance on when to use this tool versus alternatives like ise_openapi_radius_condition_get or ise_openapi_tacacs_condition_list. The deployment parameter description references ise_list_deployments, which provides some context, but the tool itself gives no when-to-use or when-not-to-use guidance.

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