ise_openapi_radius_global_exception_list

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. It doesn't state whether this is read-only, whether it requires specific permissions, what pagination behavior occurs, how results are ordered, or what the response structure looks like. It's a 'Get' so read-only is implied by convention, but nothing is disclosed about behavior beyond the bare HTTP call.

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 short and front-loaded with the scope, but it includes the raw HTTP endpoint which is redundant against the tool name. The single sentence is efficient but also lacks substance—it's minimal rather than meaningfully concise.

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 3 parameters, no output schema, no annotations, and only 33% schema documentation coverage, the description is under-specified. It doesn't describe what the returned global exception rules look like, pagination behavior, or what fields distinguish results. It also fails to disambiguate from the very similar-sounding ise_openapi_radius_exception_list sibling.

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 only 33%, meaning the page, size, and deployment parameters are largely undocumented in the schema. The deployment parameter does have a useful description in the schema (name/slug/number and reference to ise_list_deployments). However, the tool DESCRIPTION itself adds nothing about parameters; page and size semantics are left to the agent's inference. The deployment param's good schema documentation partially compensates.

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 '[Policy: Network Access] Network Access - Get global execption rules' with a specific HTTP endpoint, so it identifies the verb and resource. However, it's a thin restatement that doesn't clarify what 'global exception rules' are, and there's a misspelling ('execption'). It doesn't distinguish itself from the closely-named sibling ise_openapi_radius_exception_list.

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 when-to-use guidance is given. The sibling ise_openapi_radius_exception_list appears semantically very similar ('exception list'), but the description doesn't explain when to use one over the other. There's no mention of whether this is a complete list or paginated, no relationship to other policy tools, and no exclusions.

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