Illumio MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the output format ('summarized text format') and provides an example structure, which is helpful. However, it lacks critical behavioral details: it doesn't mention whether this is a read-only operation, potential performance impacts, rate limits, authentication requirements, or error handling. For a tool with 12 parameters and no annotations, this is a significant 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, efficient sentence that front-loads the key information: getting traffic flows in a summarized text format. It avoids redundancy and waste, though it could be slightly more structured by separating format details from the core purpose. Every part of the sentence contributes value.

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 the complexity (12 parameters, 50% schema coverage, no annotations, no output schema), the description is incomplete. It explains the output format but doesn't address the tool's behavior, error conditions, or parameter usage. For a data retrieval tool with many filtering options, more context is needed to guide effective use, especially without annotations or output schema.

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 50%, meaning half the parameters lack descriptions in the schema. The tool description adds no parameter-specific information beyond the output format example, which implies parameters like 'source', 'destination', 'port', and 'proto' but doesn't explain their mapping to schema fields or provide additional context. The description doesn't compensate for the low schema coverage, resulting in a baseline score.

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') and resource ('traffic flows from the PCE'), specifying it returns data in a 'summarized text format'. It distinguishes from the sibling 'get-traffic-flows' by emphasizing the text format output, though it doesn't explicitly compare them. The purpose is specific but could more directly contrast with the sibling tool.

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 guidance on when to use this tool versus alternatives is provided. The description mentions the output format but doesn't explain why one would choose this summarized text format over other formats (e.g., JSON or dataframe-like structures from sibling tools). There's no mention of prerequisites, limitations, or typical use cases.

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