ise_mnt_active_session_count

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

No annotations are provided, so the description carries the burden. It discloses that it returns 'raw XML' (useful behavioral info about response format), confirms it's read-only GET operation. However, it doesn't describe response structure, whether the count includes all session types, or potential error conditions. The 'raw XML' detail is helpful but limited.

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?

Two brief sentences that convey the core purpose, endpoint, and output format. Efficient and front-loaded. It could add a bit more usage context, but for a simple count GET tool, the brevity is reasonable.

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 simple count endpoint with one optional parameter, the combination of description (endpoint URL + raw XML output) and schema coverage (100%) is reasonably adequate. However, it doesn't explain what 'Active Session' means in the ISE context, whether there are filters possible, or how the count differs from other count tools (posture, profiler). No output schema exists so return structure is unspecified beyond 'raw XML'.

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 100% and the only parameter (deployment) is thoroughly documented in the schema itself, including format examples ('RADIUS Only', 'radius-only', '1') and a reference to ise_list_deployments. The description adds the endpoint context but the schema does the heavy lifting for the parameter. With just one well-documented parameter, this is appropriate.

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 clearly identifies the resource ([Sessions]), verb (Get), and specific endpoint (GET /admin/API/mnt/Session/ActiveCount). The name 'ise_mnt_active_session_count' clearly distinguishes it from siblings like ise_mnt_active_session_list (list vs. count) and ise_mnt_posture_session_count / ise_mnt_profiler_session_count (different count types).

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 states the endpoint but doesn't explicitly say WHEN to use this vs alternatives like ise_mnt_active_session_list. It doesn't mention that this returns a simple count, which would differentiate it from the session list tool. The deployment parameter helps with target selection but not tool selection.

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