ise_mnt_active_session_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. It notes 'Returns raw XML', which is helpful behavioral disclosure (format of return), but doesn't mention that this is a read-only operation, whether authentication/permissions are needed, pagination behavior, or the volume/shape of data returned. For a monitoring tool with zero annotation coverage, more disclosure is warranted.

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 compact (one sentence plus endpoint reference and return-format note). However, the endpoint URL (GET /admin/API/mnt/Session/ActiveList) is arguably structured information an agent doesn't need, while genuinely useful context (when to use vs alternatives) is absent. It earns its length but trades useful detail for a raw endpoint echo.

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 single-parameter, read-only list operation with a 100%-covered schema, this is near-minimally viable. The 'Returns raw XML' note provides some useful context, and the deployment parameter is well documented in the schema. However, the description is thin on when this differs from the adjacent session tools (auth_session_list, active_session_count) and doesn't clarify what fields/elements are returned.

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 100%, so the parameter is fully documented in the schema. The description itself adds no param information, but the schema already explains the deployment parameter thoroughly, including its 3 accepted forms and a pointer to ise_list_deployments. Baseline 3 is appropriate, nudged to 4 because the schema is exceptionally rich and self-sufficient.

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 Active Session List' uses a clear verb+resource structure and identifies it as related to sessions. The '[Sessions]' prefix groups it with sibling session tools, though it doesn't explicitly differentiate from ise_mnt_auth_session_list or other session-list tools. It's clear but lacks explicit 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 provides no guidance on when to use this tool versus alternatives like ise_mnt_active_session_count or ise_mnt_auth_session_list. It only states the API endpoint. No context is given about whether this returns all active sessions or is filtered, or what distinguishes 'active' from other session categories.

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