plotAnalytics

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

No annotations provided, so description carries full burden. It discloses return type (PNG ImageContent or error), and mentions error condition. Lacks details on auth, rate limits, or performance but is adequate for basic 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?

Description is well-structured with clear sections for purpose, supported metrics, time formats, examples, and return type. It is moderately concise; examples add length but improve clarity.

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 high parameter count (9), no annotations, and no output schema, the description is incomplete. It covers key aspects but ignores many parameters and doesn't describe chart content or relationship to sibling `queryAnalytics`.

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 0%, requiring description to explain parameters. It covers `metric` and `time` formats (from_time), and provides examples. However, it does not explain 7 other parameters (limit, interval, etc.), leaving significant gaps.

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?

Description clearly states it generates a PNG line chart for NextDNS analytics time-series, specifying action and resource. It does not explicitly differentiate from sibling `queryAnalytics` but implicitly distinguishes by mentioning chart output vs raw data.

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?

Describes when to use (visualize query trends), notes prerequisite (recent query history), and lists supported metrics. Does not explicitly state when not to use or compare to alternatives, but provides examples for clarity.

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