zdx_get_application_score_trend

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

Annotations already declare readOnlyHint=true. The description adds value by explaining the read-only nature again and clarifying the time window behavior (default 2h) and the purpose of the data (trend analysis). No contradiction with annotations.

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?

Four concise sentences, each adding value: purpose, read-only note, parameter behavior with motivation, and cross-reference to app lookup. No 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?

Covers core functionality and time window, but fails to describe optional filtering parameters or response structure (no output schema). The agent may need to infer granularity and format.

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%. The description explains the 'since' parameter (hours, default 2h) and implies 'app_id' usage, but ignores geo_id, location_id, and department_id. This leaves 3 of 5 parameters undocumented, insufficient for agent understanding.

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 it 'Get the ZDX score trend (over time) for one application,' specifying the verb and resource. It distinguishes itself from siblings like zdx_get_application by emphasizing trend data over time.

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?

Provides context: use app_id from zdx_list_applications and mentions the 'since' window default (2h) for reasoning about improvement/degradation. However, no explicit alternatives or when-not-to-use guidance are given.

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