ise_mnt_posture_session_count

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 does disclose that the tool 'Returns raw XML', which is a useful behavioral trait (the output format). However, it doesn't disclose whether this is a read-only operation, auth requirements, or what 'raw XML' means in terms of parsing expectations. The raw XML disclosure is creditable but the overall behavioral profile is thin.

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 and front-loaded with the category tag, verb, resource, and endpoint. The 'Returns raw XML' clause adds useful output context in minimal space. It's efficient with no filler, though slightly telegraphic.

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?

Given a single optional parameter, 100% schema coverage, and no output schema, the description is somewhat adequate. The raw XML return note is useful since there's no output schema. However, for a monitoring/telemetry tool with no annotations, it could note that this is a read-only status call and clarify how the XML count is structured. It doesn't fully describe behavior but is not severely lacking for a simple parameterless-ish tool.

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% for the single deployment parameter, which handles the baseline. The description itself adds no extra detail about the deployment parameter, but the schema already documents it thoroughly including name/slug/number options and the call to ise_list_deployments. The description's mention of 'raw XML' hints at output, not parameter semantics. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states the tool retrieves the active session count for posture via a specific GET endpoint ('[Sessions] Get Active Session Count (GET /admin/API/mnt/Session/PostureCount)'). The verb 'Get' plus the specific resource 'Active Session Count' and the [Sessions] category make the purpose clear. It distinguishes from siblings like ise_mnt_posture_session_count vs ise_mnt_active_session_count, though it doesn't explicitly contrast them.

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 explicit when-to-use or when-not-to-use guidance is provided. The description does not contrast this posture session count with sibling ise_mnt_active_session_count or ise_mnt_profiler_session_count to help an agent choose among the session-count tools. The deployment parameter is well explained in the schema, but no usage context or alternatives are given in the description itself.

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