ise_mnt_mnt_version

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does note it returns 'raw XML' and it's a 'System' Get operation, implying a safe read. However, it doesn't disclose what happens on unsupported deployments, error shapes, or whether the XML structure is consistent. The read operation nature is inferable from 'Get' though not explicitly stated as non-mutating.

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 concise—a single bracketed system line plus endpoint and return format. Zero wasted words, adequately front-loaded with the purpose.

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 zero-required-param simple system query with an output note (raw XML), the description is fairly complete. It lacks details about pagination, error handling, or content of the XML version payload, but for a version lookup these are minor gaps.

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% with the single deployment parameter well documented including name/slug/number formats and an explicit pointer to ise_list_deployments. No params means baseline 4 for this simple 0-required-param tool; the description itself adds the raw XML format note.

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 verb (Get), resource (Product Version), and the exact API endpoint (GET /admin/API/mnt/Version). It also notes the return format (raw XML). It doesn't explicitly distinguish from sibling tools by name, but as a version/health query it's reasonably distinct among the ise_mnt_* siblings.

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 is terse but implies usage as a basic system-version retrieval tool. There's no explicit when/when-not guidance or alternative tool mention, though the tool is fairly self-evident. The deployment param guidance (in schema) helps but isn't part of the description.

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