sophos_get_case_detection

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 a simple retrieval operation ('Get') without mentioning read-only nature, required permissions, potential response format, or any side effects. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 concise sentence of 10 words that effectively communicates the tool's purpose. It is front-loaded with the action verb 'Get' and contains no unnecessary information.

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 are 3 required parameters, no output schema, and no annotations, the description provides minimal context. It does not explain what the tool returns (e.g., detection object structure), any prerequisites (such as the case must exist), or error conditions. For a simple get operation, more context about the return value would be helpful.

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% (all three parameters have descriptions in the schema). The tool description does not add any extra meaning beyond what the schema already provides. Baseline is 3 because the schema already documents the parameters adequately.

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 action ('Get'), the resource ('a specific detection within a case'), and the method ('by detection ID'). This distinguishes it from sibling tools like 'sophos_list_case_detections' which lists all detections, and 'sophos_get_detected_exploit' which retrieves a different entity.

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 is provided on when to use this tool versus alternatives. The description only states what the tool does, not when it should be chosen over siblings like 'sophos_list_case_detections' or 'sophos_get_case'. An agent would need to infer usage from the parameter requirements.

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