List links

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

With no annotations, the description must disclose behavioral traits, but it only mentions listing, ordering, and default filtering. It does not address authentication, rate limits, pagination, scope of 'your links', or whether deleted links are excluded by default other than via the parameter. This is insufficient for a list tool.

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?

Two sentences, each earning its place. The first front-loads purpose and ordering; the second adds the default filter. No redundancy or unnecessary words.

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 no annotations, the description is too sparse. It does not mention response format, pagination behavior, maximum results, or how to interpret the output. For a list tool retrieving multiple items, this leaves significant gaps for an AI agent.

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 is 3. Description adds minimal value: it hints at the default for includeRevoked ('By default only active links are returned'), but the parameter descriptions in schema already cover the functionality. No new semantic depth is provided.

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 the tool lists short links, with ordering (newest first) and a default filter (active only). The verb 'List' and resource 'short links' are specific. However, it does not explicitly differentiate from the sibling tool 'get_link' (which retrieves a single link), though the collective purpose is distinguishable.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_link' or 'shorten_url'. The description lacks exclusions or context for optimal use. It only states default behavior, not when the tool should or should not be invoked.

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