Get AppDynamics health rule violations

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

No annotations are present, so the description carries full burden. It indicates a read-like operation ('Retrieve') but does not disclose side effects, authentication needs, rate limits, pagination, or any constraints beyond the time window. The description is minimal in behavioral context.

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, front-loaded with the verb, and contains no redundant information. Every word contributes to the purpose, making it highly concise and well-structured.

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 tool is moderately complex with 2 parameters and an output schema. The description covers the basic functionality but lacks details like default time range (though mentioned in schema), return format, or filtering capabilities. It is adequate but not fully comprehensive.

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 (application, timeRange) have detailed descriptions in the schema. The description adds no further meaning beyond the schema, as it only restates the overall purpose. With high schema description coverage, the description provides marginal added value for parameter semantics.

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' and the resource 'open / recently-closed health rule violations for an application within a time window', which is specific and distinguishes from sibling tools like appd_list_health_rules (lists rules, not violations) and appd_get_anomaly_violations (different violation type).

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 retrieving health rule violations but does not specify when to use this tool versus alternatives like appd_get_anomaly_violations or when not to use it. No explicit context or exclusion criteria are provided.

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