ops_list_tracking_short_links

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

With no annotations provided, the description carries full burden for behavioral traits. It mentions optional metric inclusion with a time window but does not disclose pagination, default behavior, authentication needs, or side effects of the list operation.

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 concise with two front-loaded sentences. It efficiently states the core purpose and the optional feature, avoiding verbosity. However, it could include more informative details without becoming overly long.

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 no output schema and six parameters, the description lacks essential context for correct invocation. It does not explain pagination, default parameter behavior, the relationship between created_from/created_to, or how include_metrics interacts with the time window. The agent cannot fully understand the tool's capabilities or constraints.

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 schema has 0% description coverage, requiring the description to compensate. It only vaguely references 'explicit time window' but does not explain any of the six parameters (limit, offset, status, created_from, created_to, include_metrics). The agent gains no semantic insight beyond the schema types.

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 lists campaign short-link configurations, with an optional extension to include per-link funnel metrics. This is specific and distinguishes it from sibling tools that update, get, or perform other operations.

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?

The description provides no guidance on when to use this tool versus alternatives like ops_get_tracking_breakdown or ops_get_tracking_summary. It does not mention exclusions or prerequisites, leaving the agent without context for selection.

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