sophos_list_isolation_exclusions

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 only states that the tool lists exclusions, but does not disclose pagination behavior (despite the schema having page/page_size), required permissions, or any side effects. The parenthetical explains what exclusions are but not the tool's behavior beyond listing.

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 (one sentence, 12 words) and front-loads the verb and resource. Every word is essential, and there is no redundancy or fluff.

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 that there is no output schema and no annotations, the description is incomplete for a list tool. It does not explain the response format, pagination behavior, or any constraints (e.g., maximum page size). The agent lacks necessary context to properly invoke and handle the results.

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%, so the description does not need to add parameter details. It adds no additional meaning beyond what is in the schema (e.g., explaining that 'page' is for pagination or 'tenant_id' is required). 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 verb 'list', the resource 'isolation exclusions', and explains what these are (IP/port combinations reachable during network isolation). It distinguishes itself from other list tools by specifying the exact resource, and siblings like sophos_create_isolation_exclusion and sophos_delete_isolation_exclusion make the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools (e.g., create, update, delete for isolation exclusions) or indicate any prerequisites or context for use. The agent must infer usage purely from the tool name and description.

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