sophos_get_adaptive_attack_protection

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

With no annotations, the burden is high. The description only indicates it retrieves settings but fails to disclose whether it is read-only, authorization requirements, or any side effects. The mention of 'temporarily increases protection' is about AAP behavior, not the tool's behavior.

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, with two sentences that are front-loaded with the core purpose. Every sentence adds value.

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?

The description provides sufficient context for a simple retrieval tool, explaining the broader purpose of AAP. However, it does not describe the structure of the returned settings. Given the lack of output schema, slightly more detail would be beneficial.

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?

Both parameters are fully described in the schema, and the description adds no new semantic guidance about their usage or format. Baseline of 3 applies due to high schema coverage.

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 it retrieves AAP settings for an endpoint, with a concise explanation of AAP's purpose, distinguishing it from its update counterpart.

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 implies this tool is used to retrieve current settings, but provides no explicit guidance on when to choose it over other get tools or the update version. No alternative names.

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