sophos_get_mdr_threat_feed

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

The description adds transparency beyond annotations by explaining that the tool returns a transactionId and requires polling sophos_get_firewall_transaction for the actual result. This asynchronous pattern is key behavioral context not conveyed by readOnlyHint and openWorldHint.

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 concise at two sentences, front-loading the main purpose and efficiently stating the follow-up action. Every word adds value with no redundancy.

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 no output schema, the description sufficiently explains the return value (transactionId) and the next step to retrieve the result. This is adequate for a read-only configuration retrieval, though it doesn't detail the configuration fields. Overall, it provides complete guidance for the interaction pattern.

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?

The input schema provides 100% coverage with descriptions for each parameter ('Tenant UUID', 'Firewall UUID'). The tool description does not add any additional meaning beyond what the schema already states, so it meets the baseline but provides no extra value.

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 'Retrieve' and the specific resource 'MDR threat-feed configuration for a specific firewall'. It also indicates the return type (transactionId) and the follow-up step, distinguishing it from siblings like sophos_create_mdr_threat_feed_indicators or sophos_search_mdr_threat_feed_indicators.

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 does not provide any guidance on when to use this tool versus alternatives. It only mentions the polling requirement after retrieval, but lacks context on prerequisites, when to prefer this tool, or what to avoid.

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