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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the tenant scope, the pagination envelope, the key item fields, and how IDs and shortCodes tie into related tools.

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 fairly dense but not bloated; each sentence contributes either the core purpose, return shape, key fields, or filter behavior. It could be tightened slightly, but the structure is logical and front-loaded with the most important information.

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?

Because there is no output schema, the description correctly explains the return envelope (items, total, page, pageSize, totalPages) and highlights important item fields. It also provides cross-references to metrics and click-count tools, making it self-sufficient for an agent deciding how to call and use the result.

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 input schema already documents all four parameters with 100% coverage, so the baseline is 3. The description adds value by explaining that search filters by title or URL and that isActive=true isolates active links, which supplements the schema descriptions.

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 action ('List all short URLs'), the resource scope ('for the current tenant'), and the included tracking metrics. It also names concrete use cases and key fields that distinguish it from related URL tools like nevent_get_short_url or nevent_list_short_url_destinations.

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?

It explains when to use the tool: discovering existing campaign links or auditing active tracking URLs. It also gives practical filter guidance for isActive and search, though it does not explicitly state when to prefer a sibling tool instead.

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