Query AppDynamics metrics (metric-data-v2)

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

The description discloses default behavior (BEFORE_NOW 30 minutes, rollup=true) and mentions surfacing granularity/long-window warnings. As a read operation without annotations, this provides adequate 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?

The description is extremely concise with three sentences, each providing essential information without redundancy.

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?

Combined with the output schema, the description covers key behavior, defaults, and warnings. It lacks mention of parallel path fan-out, but the schema covers that.

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 description adds value beyond the schema by specifying defaults and warning behavior. The schema already covers parameter descriptions, but the description enhances understanding with operational details.

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 fetches metric paths over a time range using metric-data-v2. It specifies the verb 'Fetch' and the resource 'metric paths', distinguishing it from siblings like appd_query_analytics_events.

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 when-to-use or when-not-to-use guidance is given. However, the purpose is specific enough that agents can infer usage based on sibling tool names.

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