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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: test runs are excluded from results, and the from/to window is applied to the start time specifically. It stops short of describing response shape or aggregation granularity.

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?

Purpose is front-loaded and the metric list is efficient, but '(ZUNO-SPEC-03 section 12)' is an internal spec citation that spends tokens without helping an agent decide or call. The 'Zuno flow ... nunify flow' brand switch adds avoidable ambiguity about whether two different products are involved.

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 an output schema present, return-value explanation is unnecessary, and the description covers the key behavioral caveats (test-run exclusion, start-time windowing, cross-event comparison). Only the relationship to sibling read tools (get_flow, read_analytics) is left for the agent to infer.

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 100%, so baseline would be 3, but the description adds meaning the schema does not: the from/to window filters on the flow's start time rather than any event timestamp. It says nothing about event_id/flow_id, which the schema already documents as UUIDs from list_flows and search_events.

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 names the resource (a Zuno flow's performance) and enumerates the specific metrics returned: starts, completions, step-by-step drop-off, answer choices, and cross-event comparison. It is clearly distinct from get_flow (definition) and list_flows (enumeration), though it never names those siblings explicitly to sharpen the boundary.

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?

Usage is only implied: the agent must infer that this is the tool for performance metrics rather than flow configuration. There is one useful usage constraint — 'Test runs never count' — and the optional window behavior, but no explicit guidance on when to use this versus get_flow, read_analytics, or list_flows.

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