List AppDynamics health rules

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

Description mentions optional fan-out for full definitions, hinting at multiple API calls, but does not disclose potential performance impact, rate limits, or that it is a read-only operation. With no annotations, more detail on behavior would improve transparency.

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?

Two sentences, no extraneous information, front-loaded with core purpose. Every word earns its place.

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 presence of an output schema and low complexity, the description adequately covers what the tool does. Could mention potential slowness of fan-out, but overall complete for agent decision-making.

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?

Input schema covers 67% of parameters with descriptions (context signal), but description adds context about the fan-out option (expandDetails) and its effect. The description does not significantly add beyond schema's parameter descriptions.

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 tool lists health rule summaries with specific fields (id, name, enabled) and optionally fetches full definitions. It distinguishes from siblings like appd_get_health_rule_violations which focuses on violations.

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?

No explicit guidance on when to use this tool vs alternatives like appd_get_health_rule_violations or appd_list_applications. The description assumes agent will infer from context, but lacks direct comparison or exclusions.

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