ise_mnt_session_by_ip

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a GET (read) operation and that it returns raw XML, which is useful. However, it doesn't disclose whether invalid IP addresses cause errors, what the returned XML structure contains, rate limits, auth requirements, or any other behavioral traits beyond the raw-XML note. For a session-lookup read tool this is a modest gap.

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 a single sentence that packs in the tool's purpose, the exact API endpoint, and the return format. It's efficient and front-loaded with the verb and resource. Minor waste is the 'Get Full SD' phrasing which is somewhat awkward but not harmful.

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 session-lookup tool with good schema coverage and no output schema, the description covers the essentials: what it does, the endpoint, and return format. However, no annotations exist, no output schema exists, and it doesn't clarify what 'Full SD' means or what the raw XML contains. It's adequate but leaves gaps around result interpretation and error behavior.

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 both parameters (ipaddress and deployment) are documented in the input schema. The description adds no additional parameter semantics beyond what the schema provides—no format hints, examples, or syntax details for the IP address value. With full schema coverage, baseline 3 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 states the tool gets full SD IPAddress Information via a specific API endpoint (GET /admin/API/mnt/Session/IPAddress/{ipaddress}) and returns raw XML. The '[Sessions]' prefix groups it with session tools, and the resource (IP address session data) is explicit. It's a specific verb+resource but doesn't distinguish it from siblings like ise_mnt_session_by_mac or ise_mnt_session_by_username beyond the IP address parameter in the name.

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 implies this tool is for looking up session information by IP address, which distinguishes it from sibling session tools keyed by MAC, username, endpoint IP, or ID. However, there's no explicit when-to-use guidance, no exclusions, and no mention of alternatives. The deployment parameter does note calling ise_list_deployments for options, which is helpful context.

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