ise_mnt_session_by_mac

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

No annotations provided, so the description carries the burden. 'Returns raw XML' is a useful behavioral disclosure indicating the output format. However, it doesn't state whether this is a read-only operation, what happens for unknown MAC addresses, whether it requires special privileges, or whether the returned XML structure varies. For a read operation with no annotations, some disclosure exists ('raw XML') but richer context (e.g., behavior on miss, volume/size of response) would be expected.

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?

Single compact sentence with category prefix, endpoint path, and output format disclosure. No filler or redundancy. The category [Sessions] is front-loaded, and the REST path provides precision. Could add a sentence on when to use it but remains appropriately 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 straightforward read tool with 2 params (both in schema at 100% coverage), the description is mostly adequate. But with no output schema, no annotations, and no description of return structure beyond 'raw XML', the agent gets limited sense of what to do with the response. MAC format expectations and behavior on unknown addresses are missing. Adequate but not rich for a session-inspection 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 description coverage is 100%, so the schema documents both parameters. The description adds no parameter-level semantics beyond the schema — it doesn't clarify MAC format expectations (e.g., with/without separators, case), which would be genuinely useful for a mac parameter. With full schema coverage, baseline is 3, and the description doesn't push beyond it.

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?

Clear verb+resource: 'Get Full Session Information for MAC Address' with explicit REST endpoint and category prefix '[Sessions]'. Distinguishes from siblings like ise_mnt_session_by_username/by_ip/by_endpoint_ip by specifying MAC Address lookup. Loses a point because 'Full Session Information' is somewhat ambiguous about what data is returned beyond the raw XML disclosure.

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 [Sessions] category and MAC-address-specific name imply usage but no explicit when-to-use guidance or exclusions are given. The deployment parameter references ise_list_deployments for choosing deployments, which is helpful context. However, there's no differentiation from sibling session tools like ise_mnt_session_delete_by_mac, ise_mnt_session_by_username, or ise_mnt_active_session_list beyond the name itself.

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