sophos_get_siem_alerts

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

The description does not contradict annotations (readOnlyHint=true, destructiveHint=false). It adds behavioral context beyond annotations: pagination mechanics (cursor, has_more) and the 24-hour time constraint, which are not captured in the structured fields.

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?

Three concise sentences: purpose, time constraint, pagination instructions. No unnecessary words; every sentence adds essential 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 the lack of output schema, the description adequately covers pagination fields (cursor, has_more) and the time constraint. It does not describe the alert structure, but for a retrieval tool with clear parameter schema, this is sufficient for agent understanding.

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 repeat parameter details. It adds value by explaining how the cursor and has_more fields in the response drive pagination, and clarifies that from_date must be within the last 24 hours, complementing the schema.

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 'Retrieve alerts' and the resource 'Sophos SIEM API for integration with external SIEM systems', distinguishing it from other alert tools like sophos_list_alerts and sophos_search_alerts by specifying the SIEM integration context and the 24-hour time window.

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?

It explicitly states that alerts are from the last 24 hours only, and explains pagination using cursor and has_more. However, it does not provide explicit when-not-to-use guidance or mention alternative tools for non-SIEM alert retrieval.

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