ise_mnt_profiler_session_count

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

No annotations are provided, so the description carries the disclosure burden. It notes the return is 'raw XML' and the exact REST endpoint, which is useful. However, it doesn't mention whether this is a safe read operation (despite the name suggesting it is), rate limits, or what the count represents semantically.

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 extremely short—a single line citing the endpoint and return format. It is front-loaded and zero-waste, but it omits any meaningful explanation of what a 'profiler count' is, leaving the agent to infer from the name. Concise but under-informative.

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?

With no annotations, no output schema, and a single terse sentence, the description is minimal for a tool. It doesn't explain what the profiler session count represents, how it differs from active/posture session counts among siblings, or what the raw XML looks like. For such a small tool the description should still disambiguate it from the many similar MNT session tools.

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?

The single parameter (deployment) has 100% schema coverage with a thorough description explaining accepted formats (name, slug, number) and how to list the choices via ise_list_deployments. The description adds nothing parameter-specific, but the schema already fully describes deployment, so the parameter semantics are adequately handled by the schema.

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 gets the profiler session count via a specific API endpoint and returns raw XML. The verb 'Get' plus resource 'Profiler Count' is clear, though the '[Sessions]' prefix is a bit cryptic. It doesn't differ substantially from the sibling ise_mnt_active_session_count or ise_mnt_posture_session_count in terms of clarifying what distinguishes a 'Profiler' count.

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 guidance is provided on when to use this tool versus the many sibling session-count/list tools (active_session_count, posture_session_count, auth_session_list). There is no context about typical use cases, prerequisites, or what makes this the right choice among the MNT session tools.

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