sophos_get_account_health

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

With no annotations provided, the description carries the full burden. It discloses that the tool shows protection coverage, policy compliance, and configuration issues, which is helpful but lacks details on auth requirements, rate limits, or side effects. The verb 'Get' suggests read-only behavior, but this is not explicitly stated.

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 sentence of 18 words, front-loaded with the action and resource, and efficiently conveys the tool's purpose without unnecessary detail.

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 tool's simplicity (3 parameters, all described in schema, no output schema), the description provides adequate context about the report contents. However, it does not explain the return format or filtering behavior for checks/products, which would enhance completeness.

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 already provides descriptions for all three parameters (tenant_id, checks, products). The description adds no additional meaning to the parameters beyond what the schema states, so it meets the baseline of 3 for 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 the verb 'Get' and the resource 'account health check report', and distinguishes itself from sibling tools by specifying it shows 'protection coverage, policy compliance, and configuration issues' across endpoints and network devices, a unique combination among many similar getter tools.

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 usage for checking tenant health but does not explicitly state when to use this tool versus alternatives like sophos_get_health_scores_history or sophos_get_regional_health_scores, nor does it mention prerequisites or exclusions.

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