Query AppDynamics metrics (metric-data-v2)

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

No annotations provided, so description bears full burden. It mentions default time range (BEFORE_NOW 30 min), rollup=true, and surfaces granularity and long-window warnings. However, it lacks details on error handling, authentication, or what happens with invalid metric paths.

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 with no redundant information. First sentence states purpose and API version; second sentence covers defaults and warnings. Efficient and front-loaded.

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?

With 4 parameters (2 required) and output schema existing, description covers defaults and warnings but does not explain output format, pagination, or error conditions. Could be more complete given complexity.

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 coverage is 75%, and description adds value for metricPaths by noting 'Up to 20 paths fan out in parallel'. Other parameters' defaults are already in schema. Some additional context is provided but not extensive.

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 uses metric-data-v2 to fetch one or more metric paths over a time range. It distinguishes from siblings like appd_get_metric_hierarchy (hierarchy) and other query tools by focusing on metric data retrieval.

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?

Description does not explicitly state when to use this tool versus alternatives like appd_get_metric_hierarchy or when not to use it. No prerequisites or exclusion criteria are mentioned.

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