sophos_get_siem_events

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: events are limited to the last 24 hours and pagination uses cursor and has_more. This provides behavioral details beyond the annotations, though it doesn't cover rate limits or authentication requirements.

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 only three sentences, front-loading the core purpose first. Every sentence provides essential information without redundancy or fluff. Highly efficient.

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?

With no output schema, the description could explain the return format in more detail. While it mentions cursor and has_more, it does not describe the structure of the event objects or other fields in the response. For a tool with 5 parameters, the description is somewhat concise but leaves the agent to infer the full response shape.

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 schema already describes each parameter. The description adds meaning by explaining how the cursor parameter relates to pagination (next_cursor) and mentions has_more, which is not a parameter but a response field. This enriches the agent's understanding beyond 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 'Retrieve security events from the Sophos SIEM API', which is a specific verb and resource. It distinguishes from siblings like sophos_get_siem_alerts by focusing on events rather than alerts. The time window and pagination details further clarify the scope.

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 explicitly states the tool is 'for integration with external SIEM systems' and notes the 24-hour time window, which guides appropriate use. It does not explicitly mention when not to use or provide alternative tools, but the context of sibling tools makes the purpose clear.

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