Discover AppDynamics metric paths

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

No annotations are provided, so the description carries the full burden. It discloses caching behavior (5-minute cache) and explains the hierarchical navigation. It does not cover potential issues like authentication requirements or rate limits, but given the tool's read-only nature, the disclosure is adequate.

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 just two sentences and immediately conveys the core purpose and behavior. Every sentence provides essential information without redundancy or filler.

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?

An output schema exists, so return values are already documented. The description covers the main use cases and notes caching. It does not mention pagination or limits, which are unlikely needed for a hierarchy walk. The description is complete for the tool's simplicity.

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?

Schema description coverage is 50%, and the description adds value by explaining the effect of metricPath: listing top-level folders vs children. It also clarifies the requirement to use the literal '|' character. The application parameter is covered in schema but no additional context is added in the description.

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 walks the metric hierarchy, distinguishes between listing top-level folders (no metricPath) and getting children (with metricPath). It uses a specific verb 'walk' and identifies the resource type. Among siblings, it uniquely navigates the metric hierarchy, while others like appd_query_metrics focus on metric values.

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 explicitly explains when to use it: with metricPath to drill down, without to list root nodes. It also mentions caching duration. However, it does not explicitly state when not to use this tool or suggest alternatives like appd_query_metrics for retrieving actual metric data, so it misses some guidance.

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